Just a gist, so I don’t forget it.

Configure the Credential

  • Credential Type: Ansibe Automation Platform
  • URL, as of now: the Controller URL created by the AAP 2.5 operator (still called Tower in the ACM UI :/)
  • Token: Nope, not a token that’s created using the Gateway, it’s a Controller token.
    • You can retrieve one using awx login ..., don’t forget to point the cli to the controller api. See here for relevant env vars.
    • No need to install it for testing purposes, just oc rsh into the ee container of the task pod.

So, Tower, AAP, Controller, Gateway?

Tower is the old name. Ansible Tower to be more precise. Eventually this turned into Automation Controller, part of Ansible Automation Platform (AAP).

Up until version AAP 2.4 the respective “pieces” under the umbrella of AAP had their own UIs. So Private Automation Hub (PAH), Automation Controller (AC), and Event Driven Ansible (EDA) had their own UI. One of the bigger changes with AAP 2.5 is actually a unified UI, the gateway.

What happens then?

If you e.g. want to use automtic remediation of policy violations, make sure your Job Template allows extra_vars. Especially if you jsut want to run a quick test that the integration works, you might only have a small dummy job template. In a productive scenario you’ll likely not have to remember that since you want the extra vars anyway :)