From 3f657ca28f02643fdd197d082edbc3e1432471f3 Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Fri, 31 Aug 2018 09:20:26 -0400 Subject: [PATCH] clarify priority setting (#44865) * clarify priority setting * updated as per fb --- docs/docsite/rst/user_guide/playbooks_variables.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/docsite/rst/user_guide/playbooks_variables.rst b/docs/docsite/rst/user_guide/playbooks_variables.rst index 3cb79c5968..aaf289dd93 100644 --- a/docs/docsite/rst/user_guide/playbooks_variables.rst +++ b/docs/docsite/rst/user_guide/playbooks_variables.rst @@ -866,6 +866,7 @@ Basically, anything that goes into "role defaults" (the defaults folder inside t .. note:: The previous describes the default config ``hash_behaviour=replace``, switch to ``merge`` to only partially overwrite. .. note:: Group loading follows parent/child relationships. Groups of the same 'parent/child' level are then merged following alphabetical order. This last one can be superceeded by the user via ``ansible_group_priority``, which defaults to ``1`` for all groups. + This variable, ``ansible_group_priority``, can only be set in the inventory source and not in group_vars/ as the variable is used in the loading of group_vars/. Another important thing to consider (for all versions) is that connection variables override config, command line and play/role/task specific options and keywords. For example::