redhat-cop/infra.aap_configuration

Purpose and execution model

infra.aap_configuration is an Ansible collection for configuration-as-code of Ansible Automation Platform (AAP) 2.5+. It applies declarative object definitions to AAP services through certified Ansible collections, rather than hosting an application itself. Primary packaged entry point: playbooks/configure_aap.yml; utility entry points include playbooks/get_stats.yml, playbooks/rename_objects.yaml, and playbooks/set_organization.yaml.

Dispatch orchestration

The dispatch role is the high-level ingestion and routing layer. It discovers configuration variables, including wildcard/file-tree input, then invokes the applicable domain roles. This is the main boundary between user-provided YAML inventory/vars and service-specific configuration operations.

• roles/dispatch/tasks/main.yml

• roles/dispatch/tasks/include_wildcard_vars.yml

• roles/dispatch/vars/main.yml

Shared configuration and execution behavior

Global defaults establish common AAP connection and behavioral variables; ansible_config produces local Ansible runtime configuration. Asynchronous role operations centralize result polling/error aggregation in collect_async_status, supporting either fail-fast behavior or collection into aap_configuration_role_errors.

• roles/global_vars/defaults/main.yml

• roles/ansible_config/tasks/main.yml

• roles/collect_async_status/tasks/main.yml

Automation Controller configuration

The largest domain is Controller object lifecycle management: organizations, users/teams/RBAC, credentials, projects, inventories/hosts, execution environments, templates, schedules, and workflows. Individual roles translate typed lists of desired objects into ansible.controller module calls; object dependencies imply ordering such as organizations → identities/access → credentials/projects/inventories → templates/workflows.

• roles/controller_organizations/tasks/main.yml

• roles/controller_job_templates/tasks/main.yml

• roles/controller_workflow_job_templates/tasks/main.yml

Controller execution operations

Separate command roles launch, cancel, bulk-launch, or update runtime Controller resources after definitions exist. These are action-oriented boundaries, distinct from the idempotent desired-state roles.

• roles/controller_job_launch/tasks/main.yml

• roles/controller_bulk_job_launch/tasks/main.yml

• roles/controller_inventory_source_update/tasks/main.yml

Event-Driven Ansible and platform gateway

EDA roles manage EDA identities, credential types/credentials, projects, event streams, decision environments, controller tokens, and rulebook activations. Gateway roles configure the AAP platform gateway’s auth, organizations, RBAC, routes, HTTP ports, services, service clusters/nodes/keys, and settings. They rely respectively on ansible.eda and ansible.platform APIs.

• roles/eda_rulebook_activations/tasks/main.yml

• roles/eda_controller_tokens/tasks/main.yml

• roles/gateway_services/tasks/main.yml

• roles/gateway_authenticators/tasks/main.yml

Automation Hub configuration

Hub roles manage content and access: namespaces, collections and remotes/repositories/sync, execution-environment registries/images/repositories/sync, plus users/groups/roles. This boundary uses ansible.hub modules and potentially external collection or container registries as configured inputs.

• roles/hub_collection_repository/tasks/main.yml

• roles/hub_ee_registry/tasks/main.yml

• roles/hub_publish/tasks/main.yml

Packaging, dependencies, and infrastructure

The collection is packaged for Ansible Galaxy (galaxy.yml) and declares runtime constraints in meta/runtime.yml. Required external collections are ansible.platform, ansible.hub, ansible.controller (>=4.6), and ansible.eda; target infrastructure is authenticated AAP endpoints, preferably via OAuth token. GitHub Actions provide pre-commit and automated release workflows.

• galaxy.yml

• meta/runtime.yml

• .github/workflows/release_auto.yml