summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian Coca <bcoca@users.noreply.github.com>2018-04-05 14:09:12 -0400
committerscottb <dharmabumstead@users.noreply.github.com>2018-04-05 11:09:11 -0700
commit5ad13d66aae1b3c2198e9e17dadc25910cbfdee2 (patch)
tree6c83e7bd64b03df6dc10b1c33e0fc0f646b1e298
parent9cca9a9c108124b56cd9e90130bf5ea02e3464be (diff)
downloadansible-5ad13d66aae1b3c2198e9e17dadc25910cbfdee2.tar.gz
documented actual precedence (#38009)
fixes #22025
-rw-r--r--docs/docsite/rst/user_guide/playbooks_variables.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/docsite/rst/user_guide/playbooks_variables.rst b/docs/docsite/rst/user_guide/playbooks_variables.rst
index a6edd6ce22..3c8f3f94b2 100644
--- a/docs/docsite/rst/user_guide/playbooks_variables.rst
+++ b/docs/docsite/rst/user_guide/playbooks_variables.rst
@@ -862,10 +862,10 @@ Here is the order of precedence from least to greatest (the last listed variable
* role vars (defined in role/vars/main.yml)
* block vars (only for tasks in block)
* task vars (only for the task)
- * role (and include_role) params
- * include params
* include_vars
* set_facts / registered vars
+ * role (and include_role) params
+ * include params
* extra vars (always win precedence)
Basically, anything that goes into "role defaults" (the defaults folder inside the role) is the most malleable and easily overridden. Anything in the vars directory of the role overrides previous versions of that variable in namespace. The idea here to follow is that the more explicit you get in scope, the more precedence it takes with command line ``-e`` extra vars always winning. Host and/or inventory variables can win over role defaults, but not explicit includes like the vars directory or an ``include_vars`` task.