From d2c7539ae8907d840a22d32404f625ce9893bc1e Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Wed, 4 Oct 2017 20:38:00 -0400 Subject: [PATCH] removed example for restricted facts namespace (cherry picked from commit e1fab373163ea3213fb51d3460ca5baa7ff29381) fixes #31330 --- examples/ansible.cfg | 4 ---- 1 file changed, 4 deletions(-) diff --git a/examples/ansible.cfg b/examples/ansible.cfg index 15390588af3..48b54273f33 100644 --- a/examples/ansible.cfg +++ b/examples/ansible.cfg @@ -297,10 +297,6 @@ # only update this setting if you know how this works, otherwise it can break module execution #network_group_modules=['eos', 'nxos', 'ios', 'iosxr', 'junos', 'vyos'] -# This keeps facts from polluting the main namespace as variables. -# Setting to True keeps them under the ansible_facts namespace, the default is False -#restrict_facts_namespace: True - # When enabled, this option allows lookups (via variables like {{lookup('foo')}} or when used as # a loop with `with_foo`) to return data that is not marked "unsafe". This means the data may contain # jinja2 templating language which will be run through the templating engine.