Developing Advanced Automation with Red Hat Ansible Automation Platform

The ansible-galaxy collection init command creates the directory structure for new Ansible Content Collections.

Dependencies for a collection are specified in three files: other collections under the dependencies parameter of the galaxy.yml file, Python packages in the requirements.txt file, and RPM packages in the bindep.txt file.

The ansible-galaxy collection publish command is used to publish collections on private automation hub.

The ansible-builder command creates custom automation execution environments.

The execution-environment.yml file is the configuration file for the ansible-builder command. It specifies the collections, Python packages, and RPM packages to include in the new automation execution environment.

The podman images, podman tag, and podman push commands list, tag, and push automation execution environment images to a container registry.

Automation controller can automatically pull collections and roles specified in an Ansible project's requirements.yml file, but you need to set up stored credentials so that it can authenticate to automation hub.

Automation controller can use and automatically pull custom automation execution environments, but you need to configure credentials for the container registry and specify the location of the execution environment first.