Automation (personal Ansible collection)

This repository is my personal Ansible automation collection for day-to-day tasks. It’s not intended for publication on Ansible Galaxy.

The directory layout follows the Ansible collection structure: https://docs.ansible.com/projects/ansible/latest/dev_guide/developing_collections_structure.html

Quick start

This repo is set up to be run via ansible-navigator using a pinned execution environment image (ansible-navigator.yaml).

• Inventory: hosts.yaml (see ansible.cfg)
• Defaults/config: ansible.cfg
• Execution environment: container image configured in ansible-navigator.yaml

On MacOS, start you Podman machine with:

podman machine init \
    --volume /private:/private \
    --volume /Volumes/Development:/Volumes/Development \
    --volume /Users:/Users \
    --volume /var/folders:/var/folders \
    --memory 4096 podman-machine-default
podman machine start

and install Red Hat internal root ca

podman machine ssh --username root
cd /etc/pki/ca-trust/source/anchors
# Red Hat VPN connection required
curl -k -O https://certs.corp.redhat.com/certs/Current-IT-Root-CAs.pem
update-ca-trust

Example (replace with your playbook name):

ansible-navigator run playbooks/<playbook>.yml

Execution environment (container image)

Published image tags: https://quay.io/repository/rbohne/automation?tab=tags

The execution environment build definition lives in:

• meta/execution-environment.yml

Build instructions are documented here:

• meta/README.md

Updating the pinned image

ansible-navigator.yaml pins a specific tag, for example:

ansible-navigator:
  execution-environment:
    image: quay.io/rbohne/automation:ee-YYYYMMDDHHMM

After publishing a new image tag, update ansible-navigator.yaml to point at it.