Use "override" instead of "loaded second" to be clear about what happens
Need for clarification brought up here: https://github.com/ansible/ansible/issues/9877
This commit is contained in:
parent
f9c203feb6
commit
fb5b682989
1 changed files with 1 additions and 1 deletions
|
@ -184,7 +184,7 @@ variables. Note that this only works on Ansible 1.4 or later.
|
||||||
|
|
||||||
Tip: In Ansible 1.2 or later the group_vars/ and host_vars/ directories can exist in either
|
Tip: In Ansible 1.2 or later the group_vars/ and host_vars/ directories can exist in either
|
||||||
the playbook directory OR the inventory directory. If both paths exist, variables in the playbook
|
the playbook directory OR the inventory directory. If both paths exist, variables in the playbook
|
||||||
directory will be loaded second.
|
directory will override variables set in the inventory directory.
|
||||||
|
|
||||||
Tip: Keeping your inventory file and variables in a git repo (or other version control)
|
Tip: Keeping your inventory file and variables in a git repo (or other version control)
|
||||||
is an excellent way to track changes to your inventory and host variables.
|
is an excellent way to track changes to your inventory and host variables.
|
||||||
|
|
Loading…
Reference in a new issue