Limiting plugin types 2 #150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abadger
force-pushed
the
limiting-plugin-types2
branch
from
4356357
to
0390f4e
Compare
|
To be added to the agenda once the purpose of the other alternate plugin directories are added. |
Co-authored-by: Felix Fontein <felix@fontein.de>
| * The following collections have a temporary exception to use the ``plugin_utils``, ``cli_parsers``, ``fact_diff``, and ``validate`` directories for additional plugins during the 2.10 and 3 release cycles. We will figure out a final policy which these collections will need to comply with before ansible-4: | ||
| :Those recognized by ansible-core: ``doc_fragments``, ``modules``, ``module_utils``, ``terminal``, and those listed on https://docs.ansible.com/ansible/devel/plugins/plugins.html This list can be verified by looking at the last element of the package argument of each ``*_loader`` in https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/loader.py#L1126 | ||
| :plugin_utils: For shared code which is only used controller-side, not in modules. | ||
| :sub_plugins: For other plugins which are managed by plugins inside of collections instead of ansible-core. We use a subfolder so there aren't conflicts when ansible-core adds new plugin types. |
There was a problem hiding this comment.
If we think of modules as a kind of plugin, this wording suggested by @mattclay is better:
Suggested change
| :sub_plugins: For other plugins which are managed by plugins inside of collections instead of ansible-core. We use a subfolder so there aren't conflicts when ansible-core adds new plugin types. | |
| :sub_plugins: For other plugins which are managed by non-module plugins inside of collections instead of ansible-core. We use a subfolder so there aren't conflicts when ansible-core adds new plugin types. |
There was a problem hiding this comment.
We'll do this as a separate PR.
|
This was approved at today's meeting. |
Ansible Community project plan
automation
moved this from Proposals and Discussions
to Done
Jan 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Polished policy for limiting plugin types.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION