ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

v1 variable precedence order was off.

Browse source 
Noticed that the v1 variable precedence docs list facts discovered as having a lower precedence than inventory variables. It is in reality the other way around. The v2 section gets this right.
This commit is contained in:
Timothy Appnel 2015-11-06 13:48:35 -05:00
parent 47f187b221
commit fde7c14cd0
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docsite/rst/playbooks_variables.rst
View file

@ -761,8 +761,8 @@ If multiple variables of the same name are defined in different places, they get
In 1.x the precedence is (last listed wins): In 1.x the precedence is (last listed wins):
* then "role defaults", which are the most "defaulty" and lose in priority to everything. * then "role defaults", which are the most "defaulty" and lose in priority to everything.
* then come the facts discovered about a system
* then come the variables defined in inventory * then come the variables defined in inventory
* then come the facts discovered about a system
* then comes "most everything else" (command line switches, vars in play, included vars, role vars, etc) * then comes "most everything else" (command line switches, vars in play, included vars, role vars, etc)
* then come connection variables (``ansible_user``, etc) * then come connection variables (``ansible_user``, etc)
* extra vars (``-e`` in the command line) always win * extra vars (``-e`` in the command line) always win