From d40da3ee0bddbcdba1371e5db021837a9575322a Mon Sep 17 00:00:00 2001 From: David Moreau Simard Date: Tue, 16 Feb 2021 12:24:52 -0500 Subject: [PATCH] Update 2.10 porting guide to include module index (#73615) This will help users find out where modules and plugins might have been moved. --- docs/docsite/rst/porting_guides/porting_guide_2.10.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/porting_guides/porting_guide_2.10.rst b/docs/docsite/rst/porting_guides/porting_guide_2.10.rst index 2b03959a4fb..9ca1e925b5e 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_2.10.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_2.10.rst @@ -9,7 +9,7 @@ Ansible 2.10 Porting Guide .. warning:: - In Ansible 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy `_. 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 `_. 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 `_ to find the collection a module has been relocated to. This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10.