f7dfa817ae
* `meta/` directory in collections * runtime metadata for redirection/deprecation/removal of plugin loads * a compatibility layer to keep existing content working on ansible-base + collections * a Python import redirection layer to keep collections-hosted (and otherwise moved) content importable by things that don't know better * supported Ansible version validation on collection loads
10 lines
888 B
YAML
10 lines
888 B
YAML
major_changes:
|
|
- Plugin routing allows collections to declare deprecation, redirection targets, and removals for all plugin types.
|
|
- Routing data built into Ansible 2.10 ensures that 2.9 content should work unmodified on 2.10. Formerly included
|
|
modules and plugins that were moved to collections are still accessible by their original unqualified names, so long
|
|
as their destination collections are installed.
|
|
- Collections may declare a list of supported/tested Ansible versions for the collection. A warning is issued if a
|
|
collection does not support the Ansible version that loads it (can also be configured as silent or a fatal error).
|
|
Collections that do not declare supported Ansible versions do not issue a warning/error.
|
|
- Plugins that import module_utils and other ansible namespaces that have moved to collections should
|
|
continue to work unmodified.
|