Merge pull request #8802 from garywu/patch-3
Update playbooks_variables.rst
This commit is contained in:
commit
64cb88aa3b
1 changed files with 3 additions and 5 deletions
|
@ -5,19 +5,17 @@ Variables
|
|||
|
||||
While automation exists to make it easier to make things repeatable, all of your systems are likely not exactly alike.
|
||||
|
||||
All of your systems are likely not the same. On some systems you may want to set some behavior
|
||||
or configuration that is slightly different from others.
|
||||
On some systems you may want to set some behavior or configuration that is slightly different from others.
|
||||
|
||||
Also, some of the observed behavior or state
|
||||
of remote systems might need to influence how you configure those systems. (Such as you might need to find out the IP
|
||||
address of a system and even use it as a configuration value on another system).
|
||||
|
||||
You might have some templates for configuration files that are mostly the same, but slightly different
|
||||
based on those variables.
|
||||
You might have some templates for configuration files that are mostly the same, but slightly different based on those variables.
|
||||
|
||||
Variables in Ansible are how we deal with differences between systems.
|
||||
|
||||
Once understanding variables you'll also want to dig into :doc:`playbooks_conditionals` and :doc:`playbooks_loops`.
|
||||
To understand variables you'll also want to dig into :doc:`playbooks_conditionals` and :doc:`playbooks_loops`.
|
||||
Useful things like the "group_by" module
|
||||
and the "when" conditional can also be used with variables, and to help manage differences between systems.
|
||||
|
||||
|
|
Loading…
Reference in a new issue