use of static group_vars creates a precedence problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Kevin Carter | ||
Kilo |
Fix Released
|
Medium
|
Kevin Carter | ||
Trunk |
Fix Released
|
Medium
|
Kevin Carter |
Bug Description
The current use of group_vars creates a precedence problem as they become immutable at run time. This means that even if a user were to set a new default for a role variable using a variable file and the variable was specified in the group_vars/all.yml the item in the group_vars/all.yml would always win. To fix this it is recommended that the use of group_vars be minimized in-favor of moving the basic config vars into userspace. In this case I would recommend that we create a new variable file that contains all of the group_vars/all.yml which would provide the same functionality as we have today while also providing the user the ability to arbitrarily set / reset config as they deem fit. This change would also have the added benifit of allowing the user the ability to encrypt the contents of basic config using Ansible value.
Changed in openstack-ansible: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/187102
Review: https:/