We use Ansible Automation Platform in Azure.
In AAP, I’m using Execution Environment ee-supported-rhel8, plus additional collections defined in my project:/collections/requirements.yaml file (community.general, community.vmware & checkmk.general)
I would like to follow the same pattern in ansible-navigator.
In ansible-navigator I use the same EE, defined in ansible-navigator.yaml as follows:
execution-environment:
enabled: true
image: platform..ansiblecloud.redhat.com/ee-supported-rhel8
pull:
policy: missing
But playbooks requiring community.general, community.vmware & checkmk.general fail because the required collections are missing in ansible-navigator environment.
I note, that the AAP / Automation Content / Collections / community.general / Distributions / “CLi configuration” field when copied and pasted produces the following:
[galaxy]
server_list = community
[galaxy_server.community]
url=https://platform..ansiblecloud.redhat.com/api/galaxy/content/community/
token=
Can I use the “CLi configuration” data in ansible-navigator some way to include/add/import these collections into ansible-navigator environment. If so where do I configure it?
NB: I’d rather follow the same pattern in ansible navigator rather than building a custom EE (including those collections).