Enable more flexible environment merging

Registered by Steven Hardy on 2016-06-16

Since we now support server side merging of environment files, which is good but it only supports the same "last one wins" merge strategy that we previously had in heatclient.

In some situations more flexibility is required, e.g when composing a deployment via multiple environment files where parameter key collisions will occur so add merge strategy interfaces that enable users to define how colliding keys are handled.

Blueprint information

Status:
Complete
Approver:
Thomas Herve
Priority:
High
Drafter:
Steven Hardy
Direction:
Needs approval
Assignee:
Rabi Mishra
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Zane Bitter on 2016-08-17
Completed by
Rabi Mishra on 2016-08-30

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/environment-merging,n,z

Addressed by: https://review.openstack.org/346850
    WIP Add parameter merge strategy to environments

Addressed by: https://review.openstack.org/351092
    Add new environment section for merge strategies

Addressed by: https://review.openstack.org/351093
    Add valid merge strategies

Addressed by: https://review.openstack.org/351094
    Move merge_environment to environment_util module

Addressed by: https://review.openstack.org/351095
    Improve deep merge for parameters

Addressed by: https://review.openstack.org/351096
    Refactor to use param_schemata with env merge

Addressed by: https://review.openstack.org/362035
    Add doc and reno note for environment merging

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.