From e5a1d850922d56ecd591d3d32132d9685fca3805 Mon Sep 17 00:00:00 2001 From: Sandra McCann Date: Tue, 9 Jul 2019 13:25:06 -0400 Subject: [PATCH] clarify FQCN needs for plugins (#58870) * clarify FQCN requirement, fix example --- docs/docsite/rst/collections_tech_preview.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/docsite/rst/collections_tech_preview.rst b/docs/docsite/rst/collections_tech_preview.rst index a8e76175a57..005dfb90b27 100644 --- a/docs/docsite/rst/collections_tech_preview.rst +++ b/docs/docsite/rst/collections_tech_preview.rst @@ -297,6 +297,8 @@ This works for roles or any type of plugin distributed within the collection: tasks: - include_role: name : myname.mycol.role1 + - myname.mycol.mymodule: + option1: value - debug: msg: '{{ lookup("myname.mycol.lookup1", 'param1')| myname.mycol.filter1 }}' @@ -313,8 +315,11 @@ To avoid a lot of typing, you can use the ``collections`` keyword added in Ansbi tasks: - include_role: name: role1 + - mymodule: + option1: value - debug: - msg: '{{ lookup("lookup1", 'param1')|filter1 }}' + msg: '{{ lookup("myname.mycol.lookup1", 'param1')| myname.mycol.filter1 }}' This keyword creates a 'search path' for non namespaced plugin references. It does not import roles or anything else. +Notice that you still need the FQCN for non-action or module plugins.