From 16ff4bb9375f802800e4c4d87991555ff826fd95 Mon Sep 17 00:00:00 2001 From: Kevin Fenzi Date: Mon, 4 Apr 2022 15:19:12 -0700 Subject: [PATCH] ansible-server: fix jinja in comment Signed-off-by: Kevin Fenzi --- roles/ansible-server/templates/ansible.cfg.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/ansible-server/templates/ansible.cfg.j2 b/roles/ansible-server/templates/ansible.cfg.j2 index 39cfdec8a2..6d4ee96e1e 100644 --- a/roles/ansible-server/templates/ansible.cfg.j2 +++ b/roles/ansible-server/templates/ansible.cfg.j2 @@ -74,7 +74,7 @@ callbacks_enabled=profile_roles,profile_tasks,logdetail ;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 ;allow_unsafe_lookups=False