internet/community.general
3
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2026-04-25 07:56:38 +00:00
Code Issues Packages Projects Releases Wiki 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
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):
* 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 facts discovered about a system
* then comes "most everything else" (command line switches, vars in play, included vars, role vars, etc)
* then come connection variables (``ansible_user``, etc)
* extra vars (``-e`` in the command line) always win