From 4fa2fb9c8963f1873fe20f365f43ebaa1e2db613 Mon Sep 17 00:00:00 2001 From: Jacob Floyd Date: Tue, 5 Jun 2018 19:20:21 -0500 Subject: [PATCH] Docs fix: ansible_group_priority defaults to 1 The docs committed in #28777 were inconsistent. This clarifies that the default `ansible_group_priority` is `1`.[1][2] [1] https://github.com/ansible/ansible/blob/153c9bd/lib/ansible/inventory/group.py#L40 [2] https://github.com/ansible/ansible/blob/153c9bd/lib/ansible/cli/inventory.py#L236 --- docs/docsite/rst/user_guide/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/user_guide/playbooks_variables.rst b/docs/docsite/rst/user_guide/playbooks_variables.rst index bfa26c86fac..e0386794376 100644 --- a/docs/docsite/rst/user_guide/playbooks_variables.rst +++ b/docs/docsite/rst/user_guide/playbooks_variables.rst @@ -868,7 +868,7 @@ Basically, anything that goes into "role defaults" (the defaults folder inside t If you define a variable twice in a play's ``vars:`` section, the second one wins. .. 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 'patent/child' level are then merged following alphabetical order. - This last one can be superceeded by the user via ``ansible_group_priority``, which defaults to 0 for all groups. + This last one can be superceeded by the user via ``ansible_group_priority``, which defaults to ``1`` for all groups. 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::