change duplicated label

This commit is contained in:
Sandra McCann 2020-09-21 14:53:15 -04:00 committed by Matt Clay
parent 7f62b4733d
commit bcfead8e0f
2 changed files with 4 additions and 4 deletions

View file

@ -169,7 +169,7 @@ In YAML:
webservers: webservers:
hosts: hosts:
www[01:50].example.com: www[01:50].example.com:
You can specify a stride (increments between sequence numbers) when defining a numeric range of hosts: You can specify a stride (increments between sequence numbers) when defining a numeric range of hosts:
In INI: In INI:
@ -200,7 +200,7 @@ For numeric patterns, leading zeros can be included or removed, as desired. Rang
Adding variables to inventory Adding variables to inventory
============================= =============================
You can store variable values that relate to a specific host or group in inventory. To start with, you may add variables directly to the hosts and groups in your main inventory file. As you add more and more managed nodes to your Ansible inventory, however, you will likely want to store variables in separate host and group variable files. You can store variable values that relate to a specific host or group in inventory. To start with, you may add variables directly to the hosts and groups in your main inventory file. As you add more and more managed nodes to your Ansible inventory, however, you will likely want to store variables in separate host and group variable files. See :ref:`define_variables_in_inventory` for details.
.. _host_variables: .. _host_variables:

View file

@ -193,7 +193,7 @@ Where to set variables
You can define variables in a variety of places, such as in inventory, in playbooks, in reusable files, in roles, and at the command line. Ansible loads every possible variable it finds, then chooses the variable to apply based on :ref:`variable precedence rules <ansible_variable_precedence>`. You can define variables in a variety of places, such as in inventory, in playbooks, in reusable files, in roles, and at the command line. Ansible loads every possible variable it finds, then chooses the variable to apply based on :ref:`variable precedence rules <ansible_variable_precedence>`.
.. _variables_in_inventory: .. _define_variables_in_inventory:
Defining variables in inventory Defining variables in inventory
------------------------------- -------------------------------
@ -363,7 +363,7 @@ Tips on where to set variables
You should choose where to define a variable based on the kind of control you might want over values. You should choose where to define a variable based on the kind of control you might want over values.
Set variables in inventory that deal with geography or behavior. Since groups are frequently the entity that maps roles onto hosts, you can often set variables on the group instead of defining them on a role. Remember: Child groups override parent groups, and host variables override group variables. See :ref:`variables_in_inventory` for details on setting host and group variables. Set variables in inventory that deal with geography or behavior. Since groups are frequently the entity that maps roles onto hosts, you can often set variables on the group instead of defining them on a role. Remember: Child groups override parent groups, and host variables override group variables. See :ref:`define_variables_in_inventory` for details on setting host and group variables.
Set common defaults in a ``group_vars/all`` file. See :ref:`splitting_out_vars` for details on how to organize host and group variables in your inventory. Group variables are generally placed alongside your inventory file, but they can also be returned by dynamic inventory (see :ref:`intro_dynamic_inventory`) or defined in :ref:`ansible_tower` from the UI or API:: Set common defaults in a ``group_vars/all`` file. See :ref:`splitting_out_vars` for details on how to organize host and group variables in your inventory. Group variables are generally placed alongside your inventory file, but they can also be returned by dynamic inventory (see :ref:`intro_dynamic_inventory`) or defined in :ref:`ansible_tower` from the UI or API::