ansible-server: fix jinja in comment
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
parent
9395e8822e
commit
16ff4bb937
1 changed files with 1 additions and 1 deletions
|
@ -74,7 +74,7 @@ callbacks_enabled=profile_roles,profile_tasks,logdetail
|
||||||
;action_plugins=~/.ansible/plugins/action:/usr/share/ansible/plugins/action
|
;action_plugins=~/.ansible/plugins/action:/usr/share/ansible/plugins/action
|
||||||
action_plugins={{ ansible_base }}/ansible/action_plugins:~/.ansible/plugins/action:/usr/share/ansible/plugins/action
|
action_plugins={{ ansible_base }}/ansible/action_plugins:~/.ansible/plugins/action:/usr/share/ansible/plugins/action
|
||||||
|
|
||||||
# (boolean) When enabled, this option allows lookup plugins (whether used in variables as ``{{lookup('foo')}}`` or as a loop as with_foo) to return data that is not marked 'unsafe'.
|
# (boolean) When enabled, this option allows lookup plugins (whether used in variables as or as a loop as with_foo) to return data that is not marked 'unsafe'.
|
||||||
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could represent a security risk. This option is provided to allow for backward compatibility, however users should first consider adding allow_unsafe=True to any lookups which may be expected to contain data which may be run through the templating engine late
|
# By default, such data is marked as unsafe to prevent the templating engine from evaluating any jinja2 templating language, as this could represent a security risk. This option is provided to allow for backward compatibility, however users should first consider adding allow_unsafe=True to any lookups which may be expected to contain data which may be run through the templating engine late
|
||||||
;allow_unsafe_lookups=False
|
;allow_unsafe_lookups=False
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue