You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the repo handles python modules, pip, etc. Would be great to have it also scrape existing installed Ansible Collections on the Tower nodes (collection name and version). This would be added to the final output of the playbook. For example, customer has collections installed in a custom path on the Tower nodes (/app/collections) which is set in the /etc/ansibe/ansible.cfg configuration file. Also note that, since Tower uses Ansible 2.9 the ansible-galaxy collection list command is not available.
Would be nice to add this feature.
The text was updated successfully, but these errors were encountered:
for i in `find /app/collections/ -type d -name ansible_collections -exec find {} -name "MANIFEST.*" \;`; do
echo $i | sed 's/\/app\/collections\/ansible_collections/ /'; grep version $i;
done
Currently the repo handles python modules, pip, etc. Would be great to have it also scrape existing installed Ansible Collections on the Tower nodes (collection name and version). This would be added to the final output of the playbook. For example, customer has collections installed in a custom path on the Tower nodes (/app/collections) which is set in the /etc/ansibe/ansible.cfg configuration file. Also note that, since Tower uses Ansible 2.9 the
ansible-galaxy collection list
command is not available.Would be nice to add this feature.
The text was updated successfully, but these errors were encountered: