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
plugin loader: return collection name; ansible-doc: handle ansible.builtin correctly #70026
plugin loader: return collection name; ansible-doc: handle ansible.builtin correctly #70026
Conversation
The test
The test
|
38751eb
to
1455fc3
Compare
/rebuild_failed |
ready_for_review @nitzmahone @bcoca the collection name generation now works, and it can correctly distinguish between no collection (for plugins/modules from
|
At today's project meeting, we decided that this is the wrong approach since we do not want |
890b7fc
to
da8ddd2
Compare
da8ddd2
to
8f8fc41
Compare
8eddf4b
to
035a146
Compare
rebuild_merge |
/rebuild |
@nitzmahone @samdoran thanks a lot for reviewing! |
…iltin correctly (ansible#70026) * Determine collection in plugin loader. * Fix test. * Use PluginPathContext objects in PluginLoader._plugin_path_cache instead of tuples. (cherry picked from commit 24dcaf8)
…oader: return collection name; ansible-doc: handle ansible.builtin correctly (#70572) * ansible-doc: include collection name in text output (#70401) * ansible-doc: include collection name in text output * Be more careful to not accidentally pass ansible.builtin for user-supplied modules. (cherry picked from commit f4c89ea) * plugin loader: return collection name; ansible-doc: handle ansible.builtin correctly (#70026) * Determine collection in plugin loader. * Fix test. * Use PluginPathContext objects in PluginLoader._plugin_path_cache instead of tuples. (cherry picked from commit 24dcaf8)
SUMMARY
Follow-up to #70401. Determines the collection name properly also for ansible.builtin (avoid confusion with user-supplied plugins).
ISSUE TYPE
COMPONENT NAME
lib/ansible/cli/doc.py
lib/ansible/plugins/loader.py