Previously, the openshift-applier supported the use of galaxy_requirements - which pointed to a local file with galaxy requirements. This has presented some challenges in the cases where accessing a static file like this is difficult - for example with the use of Ansible Tower. This PR introduces a new variable, galaxy_sources, which will accept a yaml list of galaxy sources and compose a temporary file that will be used with ansible-galaxy.
How should this be tested?
Define a list of galaxy_sources in the inventory and observe that these galaxy dependencies get pulled in and used correclty.
What does this PR do?
Previously, the openshift-applier supported the use of
galaxy_requirements
- which pointed to a local file with galaxy requirements. This has presented some challenges in the cases where accessing a static file like this is difficult - for example with the use of Ansible Tower. This PR introduces a new variable, galaxy_sources, which will accept a yaml list of galaxy sources and compose a temporary file that will be used with ansible-galaxy.How should this be tested?
Define a list of
galaxy_sources
in the inventory and observe that these galaxy dependencies get pulled in and used correclty.Is there a relevant Issue open for this?
N/A
Who would you like to review this?
cc: @redhat-cop/openshift-applier