Add validation for conflicting merge strategies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Rabi Mishra |
Bug Description
If you don't specify merge_strategy(
[stack@f24-devstack ~]$ cat env1.yaml
parameters:
services:
- nova
- cinder
[stack@f24-devstack ~]$ cat env2.yaml
parameters:
services:
- neutron
parameter_
services: merge
[stack@f24-devstack ~]$ cat env3.yaml
parameters:
services:
- mistral
[stack@f24-devstack ~]$ cat env4.yaml
parameters:
services:
- zaqar
parameter_
services: merge
[stack@f24-devstack ~]$ cat env_merge.yaml
heat_template_
parameters:
services:
type: comma_delimited
outputs:
service_list:
value: {get_param: services}
[stack@f24-devstack ~]$ heat stack-create test_stack -f env_merge.yaml -e env1.yaml -e env2.yaml -e env3.yaml -e env4.yaml
[stack@f24-devstack ~]$ heat output-show test_stack service_list
WARNING (shell) "heat output-show" is deprecated, please use "openstack stack output show" instead
[
"mistral",
"zaqar"
]
env3.yaml value for 'services' overwrites value from the earlier env files(env1.yaml and env2.yaml). Though this is an an expected behaviour(merge staregies are scoped to the env file and default strategy is 'overwrite', it would be good to catch that there is a conflicting merge strategy(default) for 'services' in env3.yaml.
Changed in heat: | |
milestone: | none → ocata-2 |
Changed in heat: | |
assignee: | nobody → Rabi Mishra (rabi) |
Fix proposed to branch: master /review. openstack. org/402335
Review: https:/