77bbd15bdb
This opens the door to using group_vars and host_vars in userspace, by allowing the user to define a ":" delimited list of folder that will then be used by a vars_plugin, and (maybe later) by the inventory. This can't override group_vars due to ansible precedence. We could technically have this override done by moving the group_vars into a different folder and adding it to these environment variables. Change-Id: Id22e82b01b08885a1c7b516818ca07e75f6d558f
23 lines
1.0 KiB
YAML
23 lines
1.0 KiB
YAML
---
|
|
features:
|
|
- The deployer can now define an environment variable
|
|
``GROUP_VARS_PATH`` with the folders of its choice
|
|
(separated by the colon sign) to define an user
|
|
space group_vars folder. These vars will apply but
|
|
be (currently) overriden by the OpenStack-Ansible
|
|
default group vars, by the set facts, and by the
|
|
user_* variables. If the deployer defines multiple
|
|
paths, the variables found are merged, and
|
|
precedence is increasing from left to right
|
|
(the last defined in GROUP_VARS_PATH wins)
|
|
- The deployer can now define an environment variable
|
|
``HOST_VARS_PATH`` with the folders of its choice
|
|
(separated by the colon sign) to define an user
|
|
space host_vars folder. These vars will apply but
|
|
be (currently) overriden by the OpenStack-Ansible
|
|
default host vars, by the set facts, and by the
|
|
user_* variables. If the deployer defines multiple
|
|
paths, the variables found are merged, and
|
|
precedence is increasing from left to right
|
|
(the last defined in HOST_VARS_PATH wins)
|