Ansible Playbook Development -> Migration

[Trevor]

This is one of those "not necessarily  practical" questions:

Is it possible to migrate a playbook to automation controller, 
that was NOT developed using ansible-navigator?

[Travis]

@Trevor -

Ansible playbooks are just Ansible playbooks. It doesn't matter if you use AAP 2.x with the ansible-navigator command or if you developed them pre AAP 2.x and used the ansible-playbook command, the playbooks are running the automation tasks based on the modules used in the tasks.

The bigger difference here is around the version of Ansible being used to develop the playbook and if you are using the FQCN for the module. I you are just learning Ansible and are new to Ansible, you should already be developing the playbooks with the modules using Fully Qualified Collection Names (FQCN) with the modules. 

The ansible-navigator command is just a way to let you run Ansible playbooks with the execution environment and you don't need Ansible Core installed on your local system with the ansible-playbook command. Ansible Navigator is what is launching the execution environment to run your playbook. This is why we are pushing developing with Navigator as it is super portable in that it already uses EEs. The only thing you need to ensure it runs on Ansible Controller the same was as using Navigator is to load the EEI into the Automation Controller. This will guarantee it works the same from Controller as it does when running locally with ansible-navigator.

[Travis]

@Trevor -

Again, there is no difference with ansible-navigator vs. ansible-playbook except the use of the EEI and running the playbook in an EE. So, the only slight thing you might need to ensure is that you have your "requirements.yml" file for collections or roles in the proper directory for Automation Controller to install automatically or that you select an EE that has the items already available in as part of the EEI.

[Trevor]

Love it!!!

Thank you Mr. T

[Trevor]

This is gold!!!

Thanks Travis