Ansible actions

The Ansible action provider harvests Ansible type actions from the connected Ansible Automation Platform Controller server. These actions are created automatically and reference an existing asset from an integrated Ansible installation.

Ansible Actions can reference the following:

• Job Templates
• Workflow Job Templates

Unlike SSH Actions, Ansible Actions do not define new automation content inside IBM® Runbook Automation. Instead they point to an existing automation, present in the Ansible Automation Platform Controller server, which is a job or job workflow template.

When an Ansible Action runs, it calls the specific "launch" operation of that template on the connected Ansible Automation Platform Controller server. If the template requires prompting for specific variables, these variables are sent by Runbook Automation. Runbook Automation allows these variables to be defined as Action parameters.

The integration with Ansible has been verified with Ansible Automation Platform 2.4 and Automation Controller 4.5.2, and with Ansible Automation Platform 2.5 and Automation Controller 4.6.2. The set of parameters that can be actively used in the related automation actions is limited to what is documented at Job Template parameters and surveys.

See the topics that follow this section for more information about Ansible Actions.

• Harvesting Ansible actions
• Ansible Action interactions
• Job Template parameters and surveys