From f40d39bc92179c73ec1272b3bb5a1164ef9882b9 Mon Sep 17 00:00:00 2001 From: James Cammarata Date: Thu, 22 Aug 2013 23:35:23 -0500 Subject: [PATCH] Minor formatting change --- docsite/latest/rst/playbooks.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/latest/rst/playbooks.rst b/docsite/latest/rst/playbooks.rst index cd3b540ffde..bb0b6f372c1 100644 --- a/docsite/latest/rst/playbooks.rst +++ b/docsite/latest/rst/playbooks.rst @@ -149,7 +149,7 @@ These variables can be used later in the playbook like this:: {{ varname }} -Variables are passed through the Jinja2 templating engine, and support the use of filters to modify the variable (for example: {{ varname|int }} ensures the variable is interpreted as an integer). To learn more about Jinja2, you can optionally see the `Jinja2 docs `_ - though remember that Jinja2 loops and conditionals are only for 'templates' in Ansible, in playbooks, ansible has the 'when' and 'with' keywords for conditionals and loops. +Variables are passed through the Jinja2 templating engine, and support the use of filters to modify the variable (for example: `{{ varname|int }}` ensures the variable is interpreted as an integer). To learn more about Jinja2, you can optionally see the `Jinja2 docs `_ - though remember that Jinja2 loops and conditionals are only for 'templates' in Ansible, in playbooks, ansible has the 'when' and 'with' keywords for conditionals and loops. If there are discovered variables about the system, called 'facts', these variables bubble up back into the playbook, and can be used on each system just like explicitly set variables. Ansible provides several of these, prefixed with 'ansible', which are documented under 'setup' in the module documentation. Additionally,