The ansible.cfg.j2 template is using the wrong API paths for AAP 2.5 in ee_builder role. This effects the pulling of collections into the EE during the ansible-builder phase.
Issue Type
I imagine an extra variable will need to be added to specify whether the user is running AAP 2.4 or 2.5 as it would break the role between versions.
Bug Report
Desired Behavior
API paths should be https://{{ ee_ah_host }}/pulp_ansible/galaxy/<remote_name>/
Actual Behavior
API paths are currently https://{{ ee_ah_host }}/api/galaxy/content/<remote_name>/
STEPS TO REPRODUCE
Any one using the ee_builder role on an AAP 2.5 will run into the issue if they've specified ee_pull_collections_from_hub to true
I wrote something to hopefully fix this but haven't had a chance to test it yet, I have the PR open. If you can test it out that would be helpful, if not I should be able to get to it soon
Summary
The ansible.cfg.j2 template is using the wrong API paths for AAP 2.5 in ee_builder role. This effects the pulling of collections into the EE during the ansible-builder phase.
Issue Type
I imagine an extra variable will need to be added to specify whether the user is running AAP 2.4 or 2.5 as it would break the role between versions.
Desired Behavior
API paths should be
https://{{ ee_ah_host }}/pulp_ansible/galaxy/<remote_name>/
Actual Behavior
API paths are currently
https://{{ ee_ah_host }}/api/galaxy/content/<remote_name>/
STEPS TO REPRODUCE
Any one using the ee_builder role on an AAP 2.5 will run into the issue if they've specified ee_pull_collections_from_hub to true