You have tested running a Playbook that depends on the Podman collection with
ansible-navigator in your custom Execution Environment. Now it’s time to use the custom EE with the Podman collection in automation controller.
PAH should be configured correctly in your lab environment by the initial installation, just check to learn where it’s done:
Automation Hub Container Registrypoints to PAH
You can find the Authentication URL on your private automation hub by navigating to Execution Environments, select the EE you want to use and then in Details.
Execution Environmentsand add the new EE
Get the image location from your PAH: In Execution Environments click on the image and you will see an example command to pull the image which has the image name included.
This time we’ll run the Playbook you used before, but in your custom EE! That means we shouldn’t have to use a
requirements.yml file to automatically load the needed collection because
containers.podman is already included in the EE.
https://github.com/ansible-learnfest/ee-flow.gitwith the branch
wo-requirements. This branch contains no
requirement.ymlto automatically add the collection. If you want to double check, have a look a the Job output and you’ll notice that no collection was installed during project sync.
Using private automation hubchapter, or just create a copy of it. We want to make one change in the copied job template:
You can disable automation controller’s feature to automatically download and install Ansible Collections by navigating to Settings -> Job Settings. Here you can disable
Enable Collection(s) Download and
Enable Role Download. By doing so, you force the automation controller to only use collections which are already part of the execution environment. This can be useful to make sure the collection inside the EE is not overridden by a newer version provided by your private automation hub or Ansible Galaxy. This gives you more predictable and reproducible Ansible Playbook execution.