Page History

At the moment, at migrate/update time, there is a merge of the old and new properties helm by the instance. However, this merge of properties does not take account of nested maps that need to be recursively merged.

In order to apply the recursive update it needs to implement the recursive properties validation.
Using same methods for the validation, we can convert properly what is supposed to be a Map by definition.

Work Breakdown:

• Create reusable methods to retrieve data structure of the properties
• Implement validation in creation, update and migrate of the instance
• Implement recursive merge and add eventually additional validations in migration
• participant needs same recursive merge, so needs the full service template in priming time

Unresolved question:

...

Solution 1

For any "property" of the new Map, recursive update will be apply only if in both new and old map, the type of the value "map.get(property)" are Map.

Example

properties:
  chart:
    chartId:
      name: acelement
      version: 0.1.0
    namespace: default
    releaseName: acm-starter
    podName: acm-starter

properties:
  chart:
    releaseName: acm-starter-new
    podKey: 123
    podName: null

properties:
  chart:
    chartId:
      name: acelement
      version: 0.1.0
    namespace: default
    releaseName: acm-starter-new
    podKey: 123

...