Update 2.10 porting guide to include module index (#73615)
This will help users find out where modules and plugins might have been moved.
This commit is contained in:
parent
00bd0b893d
commit
d40da3ee0b
1 changed files with 1 additions and 1 deletions
|
@ -9,7 +9,7 @@ Ansible 2.10 Porting Guide
|
||||||
|
|
||||||
.. warning::
|
.. warning::
|
||||||
|
|
||||||
In Ansible 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. Your playbooks should continue to work without any changes. We recommend you start using the fully-qualified collection name (FQCN) in your playbooks as the explicit and authoritative indicator of which collection to use as some collections may contain duplicate module names.
|
In Ansible 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. Your playbooks should continue to work without any changes. We recommend you start using the fully-qualified collection name (FQCN) in your playbooks as the explicit and authoritative indicator of which collection to use as some collections may contain duplicate module names. You can search the `index of all modules <https://docs.ansible.com/ansible/2.10/collections/index_module.html>`_ to find the collection a module has been relocated to.
|
||||||
|
|
||||||
This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10.
|
This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue