Enable more flexible environment merging
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:
- newton-3
- Started by
- Zane Bitter
- Completed by
- Rabi Mishra
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP Add parameter merge strategy to environments
Addressed by: https:/
Add new environment section for merge strategies
Addressed by: https:/
Add valid merge strategies
Addressed by: https:/
Move merge_environment to environment_util module
Addressed by: https:/
Improve deep merge for parameters
Addressed by: https:/
Refactor to use param_schemata with env merge
Addressed by: https:/
Add doc and reno note for environment merging