Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
I think we should implement an action group since this can be quite useful. I guess sooner or later someone will open a feature request for this, anyway.
amazon.aws and community.aws seem to share the action group
aws
. I suggest the same here: community.vmware already usesvmware
, so let's also use it here.Additionally, we might consider renaming the action group of the modules in vmware.vmware_rest from
vmware_rest
tovmware
, but this is off-topic here. Just wanted to mention it as an idea.If you think it would be better to not share action groups between those collections, that's also fine for me. The important thing is to have one in order to allow people to use module defaults. If you think it would be better to have a unique name for the action group, it would be great if you could suggest one.
ISSUE TYPE
COMPONENT NAME
meta/runtime.yml
ADDITIONAL INFORMATION
ansible-collections/vmware.vmware_rest#440