removed example for restricted facts namespace
(cherry picked from commit e1fab37316
)
fixes #31330
This commit is contained in:
parent
e167c9338c
commit
d2c7539ae8
1 changed files with 0 additions and 4 deletions
|
@ -297,10 +297,6 @@
|
||||||
# only update this setting if you know how this works, otherwise it can break module execution
|
# 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']
|
#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
|
# 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
|
# 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.
|
# jinja2 templating language which will be run through the templating engine.
|
||||||
|
|
Loading…
Reference in a new issue