From 00ed2b811fd15461fef538fb3ad67d645e48dd66 Mon Sep 17 00:00:00 2001 From: David Wheaton Date: Sat, 8 Mar 2014 13:53:16 -0800 Subject: [PATCH] Update playbooks_variables.rst incorrect/confusing wording in Jinja2 note? --- docsite/rst/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index bdb31577ed1..0ab668135cf 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -101,7 +101,7 @@ Inside a template you automatically have access to all of the variables that are it's more than that -- you can also read variables about other hosts. We'll show how to do that in a bit. .. note:: ansible allows Jinja2 loops and conditionals in templates, but in playbooks, we do not use them. Ansible - templates are pure machine-parseable YAML. This is a rather important feature as it means it is possible to code-generate + playbooks are pure machine-parseable YAML. This is a rather important feature as it means it is possible to code-generate pieces of files, or to have other ecosystem tools read Ansible files. Not everyone will need this but it can unlock possibilities.