-
Notifications
You must be signed in to change notification settings - Fork 23.9k
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
Adjust action groups to moved modules #72428
Conversation
@geerlingguy @tima similar PRs like ansible-collections/community.docker#17 will be needed in your collections as well for this to work. |
/rebuild_failed |
/rebuild_failed |
/rebuild_failed |
@gundalow I think the tests are broken (maybe just temporarily), unrelated to this PR. |
@felixfontein the k8s module is not moving to the okd collection; that collection just has an alias/override of the k8s module customized for OpenShift. |
@geerlingguy thanks! I've removed community.okd from this PR then. |
@felixfontein though the oc plugin is moving from community.general to community.okd, and the k8s_auth plugin moved from community.kubernetes to community.okd. |
This reverts commit 812b5aa.
@geerlingguy ok, in that case I reverted the last commit :) It's then needed for the k8s_auth module. (Module defaults are not used for non-action plugins, so the oc connection plugin doesn't matter.) |
@@ -1357,9 +1357,9 @@ def get_action_args_with_defaults(action, args, defaults, templar, redirected_na | |||
'aws': ['amazon.aws', 'community.aws'], | |||
'azure': ['azure.azcollection'], | |||
'cpm': ['wti.remote'], | |||
'docker': ['community.general'], | |||
'docker': ['community.general', 'community.docker'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a blocker to this PR, but this should be moved to config (really should not be a thing in core at all, but setlingling for moving into config).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was assuming that this is a placeholder anyway until the action groups feature is fully designed and implemented.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that is tentatively slated for 2.11
/rebuild_failed |
/rebuild |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK to me
@geerlingguy @bcoca @sivel @gundalow thanks for reviewing! |
* Support docker and k8s action groups for moved modules in community.docker and community.kubevirt. * Also support k8s action group for community.okd. * Also add kubernetes.core. * Adjust PR #. * Fix changelog fragment. * Remove community.okd. * Revert "Remove community.okd." This reverts commit 812b5aa. (cherry picked from commit c7a4b39)
SUMMARY
The docker modules, kubevirt modules and the k8s module are moving to other collections:
The k8s module is moving from community.kubernetes to community.okd (already in progress, collection with module already released).Right now, support for the docker and k8s action groups / module default groups does need to know in which collection the affected modules / action plugins are contained. Therefore, lib/ansible/executor/module_common.py needs to be updated (and this change backported to stable-2.10) for the moves to work flawlessly, and to avoid breaking playbooks and roles.
The old names must not be removed either to avoid breakage with older (current) versions of the collections.
CC @s-hertel @gundalow @geerlingguy @tima
ISSUE TYPE
COMPONENT NAME
lib/ansible/executor/module_common.py