-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: add option(s) to ansible-playbook to check modules are found and what content source they come from #68989
Comments
Files identified in the description: If these files are incorrect, please update the |
Same as #69334? self-promotional plug: https://github.com/AlanCoding/ansible-locate |
Files identified in the description: If these files are incorrect, please update the |
Files identified in the description: If these files are incorrect, please update the |
Thank you very much for your submission to Ansible. It means a lot to us that you've taken time to contribute. Unfortunately, this issue has been open for some time while waiting for a contributor to take it up but there does not seem to have been anyone that did so. So we are going to close this issue to clear up the queues and make it easier for contributors to browse possible implementation targets. However, we're absolutely always up for discussion. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below: In the future, sometimes starting a discussion on the development list prior to proposing or implementing a feature can make getting things included a little easier, but it's not always necessary. Thank you once again for this and your interest in Ansible! |
SUMMARY
There is a need to provide tooling for the following use cases:
I have a playbook and I want to check to see what modules I am using are not in ansible-base, rather now they live in collections. I want to know what collection they live in without having to manually search through routing.yml. I prefer not to know
routing.yml
exists. I want to know which ones these are without having to run the playbook and see where it breaks, following including roles andinclude_tasks
.I have a playbook and have installed in my environment a bunch of collections, I want to check and see what collection is going providing each module before running the playbook.
These address both users that are taking advantage of "tombstoning" as well as those who would like to update their content to explicitly use certain collections.
It provides a more sane way of developing and linting ansible content without having to take the approach of "just run it and see where blows up, then run it again and see where it blows up the next time" which is not a great development experience.
Currently, in order to figure out what collections my playbooks depend on, I either need to read ever task of every playbook and role and know intimately what has been moved (e.g. have routing.yml memorized) or run it and let it blow up, then manually look up what collection it is now hosted in by looking at https://github.com/ansible/ansible/blob/devel/lib/ansible/config/routing.yml .
#67684 is putting place "tombstoning" aims to enable people to not have to re-write their playbooks to be able to run with ansible 2.10, given that a collection is installed that provides the content that ansible knows to try based on https://github.com/ansible/ansible/blob/devel/lib/ansible/config/routing.yml
If indeed we are capable of doing such routing, then we should be capable of reporting to the user what that routing is without having to actually execute the playbook tasks.
ISSUE TYPE
COMPONENT NAME
collections
routing.yml
ADDITIONAL INFORMATION
This feature would allow me to:
Could look something like this:
Most basic, just show my modules mapped out w/ FQCN, have it behave like
--list-tasks
when it finds all some source for each module and show the source, have it fail like--syntax-check
when it fails.Alternatively, we might not need
--content-check
at all and all of the functionality could be rolled into--list-tasks
and--syntax-check
The text was updated successfully, but these errors were encountered: