From b0c48971965d96efdb4b47cb5be4f3ee8ed00ded Mon Sep 17 00:00:00 2001 From: Gary Wu Date: Thu, 28 Aug 2014 09:39:14 -0500 Subject: [PATCH] Update playbooks_variables.rst --- docsite/rst/playbooks_variables.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index 1e61cecbb01..e20e1d6dbe0 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -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.