Ansible Automation interactions

Interactions based on connection state

Beginning with the June 2021 release, the Ansible® Automation Provider automatically converts job templates into automations. These automations are read only in Runbook Automation, but they pick up any change to the original template made in Ansible. To change any aspect of the automation, you can edit the original template.

If you change the Ansible connection, for example to point to another Ansible Automation Platform Controller server with different templates, the previously harvested templates are no longer visible from the Automations page. Runbooks containing those templates can no longer run the automations. Instead, the templates from the new Ansible Automation Platform Controller server are visible.

If you change the Ansible connection back to a previous configuration, the automations that are harvested from this connection reappear, together with their statistics. All runbooks that contain those templates are again able to run those automations.

All runbook instances continue to be fully visible, independent of the state of the Ansible connection.

Manually created Ansible Automations

Before the June 2021 release, the Ansible Automation Provider did not harvest the automations from Ansible. Instead, you created and edited the Ansible Automations yourself.

Those Automations are not deleted. They are the only Ansible Automations that users can edit or delete. Because the new Automation Provider harvests these, they might be duplicates of harvested automations. It is possible, but not required, to replace the old automations in all runbooks with the newly harvested automations and then safely remove the manually created automations.