mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
parent
8262f7bfac
commit
1f42fd9964
2 changed files with 3 additions and 7 deletions
|
@ -282,7 +282,7 @@ This makes a dynamic group of hosts matching certain criteria, even if that grou
|
||||||
|
|
||||||
- hosts: all
|
- hosts: all
|
||||||
tasks:
|
tasks:
|
||||||
- group_by: key=${ansible_distribution}
|
- group_by: key={{ ansible_distribution }}
|
||||||
|
|
||||||
# now just on the CentOS hosts...
|
# now just on the CentOS hosts...
|
||||||
|
|
||||||
|
|
|
@ -147,13 +147,9 @@ The `vars` section contains a list of variables and values that can be used in t
|
||||||
|
|
||||||
These variables can be used later in the playbook like this::
|
These variables can be used later in the playbook like this::
|
||||||
|
|
||||||
$varname or ${varname} or {{ varname }}
|
{{ varname }}
|
||||||
|
|
||||||
If you ever want to do anything complex like uppercasing a string, {{ varname }} is best, as it uses the Jinja2 templating engine. It is a good idea to get in the habit of using this form most of the time when the output is to be a string.
|
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 interpretted as an integer). To learn more about Jinja2, you can optionally see the `Jinja2 docs <http://jinja.pocoo.org/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 just referencing the value of another simple variable though, it's fine to say $x or ${x}. This is common for when a datastructure has a member that is the value of another datastructure.
|
|
||||||
|
|
||||||
To learn more about Jinja2, you can optionally see the `Jinja2 docs <http://jinja.pocoo.org/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
|
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,
|
of these, prefixed with 'ansible', which are documented under 'setup' in the module documentation. Additionally,
|
||||||
|
|
Loading…
Reference in a new issue