Automated Execution-Environment Builder - Ansible Automation Platform 2

Note	fork or clone repo so that you can use your own GitHub Secrets and workflow.

Content

• Purpose

• Workflow

• Prereqs

• Playbook

• Status

Purpose

This repo contains everything needed to create a closed loop automated way to create Execution Environments for Ansible Automation Platform.

Workflow

A workflow will begin automaticaly when ee_builder.yml has been updated and a PR has been merged to the main branch.

Workflow Steps

• Launch ubuntu-latest runner

• Checkout main branch

• Install Python dependencies

• Install Ansible collections

  • awx.awx

  • infra.ee_utilities

• Runs ee_builder.yml with EE_REGISTRY_PASSWORD and AH_TOKEN GitHub Secrets being passed in as Extra Vars

This will create an image and push to remote image registry, ie. DockerHub, Quay, or Private Automation Hub

Prereqs

GitHub Secrets

• Update GitHub Secrets

  • AH_TOKEN - Galaxy or Automation Hub API Key (needs to provide creds for ee_ah_host)

  • EE_REGISTRY_PASSWORD - DockerHub or Image Registry Password (needs to provide creds for ee_registry_dest)

Note	These secrets get passed during the GitHub Actions workflow. This method is easy for demo but maynot meet production requirements "Passing Secrets"

Playbook

The steps below describe what to update in the ee_builder.yml in order to successfuly create an execution environment.

Example - Need to update if forked

1. "ee_registry_dest" - Currently set to my personal "Quay.io Repo"

2. "ee_registry_username" - Update to reflect username for the ee_registry_dest value

3. "ee_ah_host" - FQDN of Hub to get collections, I chose "Ansible Galaxy" for ease of use

Status

Figure 1. Ansible Execution Environment Builder