Now that you have learned how all the stages of building, testing, pushing and using a custom Execution Environment work, do it without help from the guide. Here are your tasks:
enforce-selinux.yml
in https://gitlab.com/ansible-learnfest/playbook-challenge.git
should be run with your custom EE against your managed nodes.redhat.rhel_system_roles
that is not part of your EE yet.So this is what you have to do:
ansible.cfg
like this (fill in your AH token):[galaxy]
server_list=rh-certified,published,community
[galaxy_server.rh-certified]
url=https://hub-<student name>.learnfest.ansible-labs.de/api/galaxy/content/rh-certified/
token=<your token>
[galaxy_server.published]
url=https://hub-<student name>.learnfest.ansible-labs.de/api/galaxy/content/published/
token=<your token>
[galaxy_server.community]
url=https://hub-<student name>.learnfest.ansible-labs.de/api/galaxy/content/community/
token=<your token>
You can find the URL for each repository in your private automation hub in the tab Repository Management and you can create an API token under API token management. Double check you did actually synchronize the ‘redhat.rhel_system_roles’ collection to your private automation hub!
ansible-builder
in the definition file to read the ansible.cfg
file:[...]
dependencies:
galaxy: requirements.yml
python: requirements.txt
system: bindep.txt
ansible_config: /path/to/ansible.cfg
[...]
redhat.rhel_system_roles
to your EE build definition (requirements.yml
) and build a new version.ansible-navigator
inspect the new image to contain the needed collectionansible-navigator
like you did in the “Build an execution environment” chapter
https://gitlab.com/ansible-learnfest/playbook-challenge.git
enforce-selinux.yml
Playbook and the new version of the EE