Ansible Developer Demo

Demo Scenarios

1. Create Custom Collection
2. Create Custom EE with collection from point 1
3. Upload Custom EE to On-Prem Automation Hub
4. Use Custom Collection with ansible-navigator
5. Use Custom Collection with Controller

1. Create Custom Content Collection

Collection Skeleton

ansible-galaxy collection init --init-path ./ jacek.custom_app

Place Content

Place Roles, modules, plugins etc.

In my case I will copy previously prepared roles and copy modules from ansible.posix collection

Build collection

In collection dir start following:

ansible-galaxy collection build

Publish collection (Automation Hub On-Prem)

1. Create namespace on Hub
2. Upload collection archive

2. Create Custom EE with custom_app collection

Login to registry

podman login registry.redhat.io

Create all required files for custom_app_ee

requirements.yml

---
collections:
  - jacek.custom_app

ansible.cfg

[galaxy]
server_list = published_repo

[galaxy_server.published_repo]
url=https://jskauthub.redhat.lab/api/galaxy/content/published/
token=

ansible-builder image definition file - custom_app_ee_def.yml

version: 1

build_arg_defaults:
  ANSIBLE_GALAXY_CLI_COLLECTION_OPTS: "-v"
  EE_BASE_IMAGE: 'registry.redhat.io/ansible-automation-platform-22/ee-minimal-rhel8'
  
ansible_config: 'ansible.cfg'

dependencies:
  galaxy: requirements.yml
#  python: requirements.txt
#  system: bindep.txt

additional_build_steps:
  prepend: |
    RUN whoami
    RUN cat /etc/os-release
  append:
    - RUN echo This is a post-install command!
    - RUN ls -la /etc

Build custom EE

ansible-builder build -f custom_app_ee_def.yml -t custom_app_ee

Push to On-Prem Automation Hub

podman login jskauthub.redhat.lab --tls-verify=false
podman push Image_ID docker://jskauthub.redhat.lab/custom_aap_ee --tls-verify=false