Capture an AAP deployment as configuration-as-code

Problem and outcome

Playbooks and roles often already live in Git. The Controller objects that launch them (organizations, credentials, projects, inventories, and job templates) often grow in the UI and are not versioned. Crane captures that deployment as a Git-native configuration-as-code repository so it can be reviewed and applied onto AAP.

Who it is for

AAP administrators who need disaster recovery, environment promotion, an audit trail, or an upgrade path without treating the Controller UI as the source of truth.

Prerequisites

• A custom engineering engagement. Crane (Beta) is not part of the self-managed subscription catalog.
• A source controller to export from: AAP 2.4, AAP 2.6 or later, or AWX.
• An apply target of AAP 2.6 or later. If you omit a target, apply is still AAP 2.6.
• A Git remote you choose for the packaged repository.

Technical walkthrough

Crane connects to a controller, exports configuration, packages a Red Hat-aligned apply repository, and pushes that repository to your Git host. The recording on this page shows export from AWX and apply onto AAP 2.7. A second recording on the Crane page shows export from AAP 2.4 and apply onto AAP 2.7.

AWX is an export source in that demonstration. AWX is not the self-managed BacklogZero control plane.

BacklogZero's role

BacklogZero generates playbooks and creates AAP job templates on a self-managed subscription. Crane is the separate configuration-as-code compiler for the Controller objects around those playbooks. Crane is a deterministic compiler. It is not an AI-authored YAML repo and it is not a backup utility.

Evidence

The embedded recording is the AWX-to-AAP 2.7 demonstration published on the Crane page. It shows the export and apply path. It is not a customer case study.

Operational considerations

• Crane (Beta) is currently available in custom engineering engagements.
• Crane does not export credential secrets from the source controller.
• Beta limits: no unattended GitOps drift loop, no one-click apply from the UI, no job-history export, no credential secret export, and no project or repo migration.
• Auto-Sync and Best Practices assess are available. Fleet reconciliation and full promotion workflows are later.
• This site does not claim a compliance certification.

Business implications

Configuration that lives only in the Controller UI is harder to review, promote, and recreate. Crane puts that configuration in Git so a person can review the commit. This page does not state a measured cost or time saving.

Next steps

Read the full Crane limits and source/target table, or request a scoping conversation if you want engineers to run this with you. The self-managed subscription remains on pricing.