Chapter 3. Common automation execution environment scenarios
Use the following example definition files to address common configuration scenarios.
3.1. Updating the automation hub CA certificate Copy linkLink copied to clipboard!
Use this example to customize the default definition file to include a CA certificate to the additional-build-files section, move the file to the appropriate directory and, finally, run the command to update the dynamic configuration of CA certificates to allow the system to trust this CA certificate.
Prerequisites
-
A custom CA certificate, for example
rootCA.crt.
Customizing the CA certificate using prepend_base means that the resulting CA configuration appears in all other build stages and the final image, because all other build stages inherit from the base image.
3.2. Using automation hub authentication details when building automation execution environments Copy linkLink copied to clipboard!
Use the following example to customize the default definition file to pass automation hub authentication details into the automation execution environment build without exposing them in the final automation execution environment image.
Prerequisites
-
You have created an automation hub API token and stored it in a secure location, for example in a file named
token.txt. - Define a build argument that gets populated with the automation hub API token:
export ANSIBLE_GALAXY_SERVER_AUTOMATION_HUB_TOKEN=$(cat <token.txt>)
export ANSIBLE_GALAXY_SERVER_AUTOMATION_HUB_TOKEN=$(cat <token.txt>)