From 1f2f292290f1bf57968390d71254d9ebcd14c813 Mon Sep 17 00:00:00 2001 From: Brian Williams Date: Tue, 2 Mar 2021 10:10:08 -0500 Subject: [PATCH] Fix invalid yaml in collections_using.rst (#73727) Fix invalid quoting. --- docs/docsite/rst/user_guide/collections_using.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/user_guide/collections_using.rst b/docs/docsite/rst/user_guide/collections_using.rst index 0f1bb65a3d9..accab057fc5 100644 --- a/docs/docsite/rst/user_guide/collections_using.rst +++ b/docs/docsite/rst/user_guide/collections_using.rst @@ -332,7 +332,7 @@ In a playbook, you can control the collections Ansible searches for modules and option1: value - debug: - msg: '{{ lookup("my_namespace.my_collection.lookup1", 'param1')| my_namespace.my_collection.filter1 }}' + msg: '{{ lookup("my_namespace.my_collection.lookup1", "param1")| my_namespace.my_collection.filter1 }}' The ``collections`` keyword merely creates an ordered 'search path' for non-namespaced plugin and role references. It does not install content or otherwise change Ansible's behavior around the loading of plugins or roles. Note that an FQCN is still required for non-action or module plugins (for example, lookups, filters, tests).