Demo ·
Crane can export from AWX
Crane can pull Configuration-as-Code from community AWX for you to immediately apply onto AAP.
Sprint 116 adds AWX as a Crane export source
- CRANE
- AWX
- AAP
What you are seeing
Crane's job is Configuration-as-Code: export from a controller, reshape the payload when versions differ, apply onto a target. Sprint 116 expands that matrix: several sources, several targets, one wizard. See the Crane product page for sources, targets, and beta status.
This recording is Crane → CaC export. Pick a source, pick a target, save a draft. Builds to fit the target you chose.
Crane now supports several automation platform sources and targets, including:
| Export from | Apply to | What Crane does |
|---|---|---|
| AAP 2.4 | AAP 2.6+ | 2.4→2.6 rename |
| AAP 2.6+ | AAP 2.6+ | Same-platform apply |
| AWX | AAP 2.7 | Export from AWX; apply onto AAP 2.7 |
If you omit a target, apply is still AAP 2.6.
Why it matters
- AWX operators can export CaC from the controller they actually run and land it on AAP.
- AAP operators do not have to change anything. 2.6 is still the documented golden path.
Currently Available in BacklogZero Custom Engagements
Crane profile on. Open Crane → CaC export.
- Confirm source defaults to 2.6+, with “AAP Controller URL” labels.
- Choose AWX 24.x (experimental) — labels become Controller URL / Controller Token.
- Leave apply on AAP. Save the draft and reload — source should still be AWX.
- If you have a lab AWX and a UI-created PAT, probe/export from Crane. Do not put the token in git.
Still open
AWX as an export source stays experimental until an operator empty-diff checklist matches the AAP 2.6 bar. /aap and MCP names stay as they are. Comment write-back, Crane MCP mutations, and cancel/relaunch remain later work.
Crane (Beta)
Currently available to custom engagement customers.