Rules in ConfigData can only replace existing nodes in target file, can't add new ones.

[dee0]

This is related to #72

See the comment there about the case where no reasonable default is possible. #72 combined with this make it difficult to manage a large number of config values, particularly when they are organized into a structure.

The hack that I came up with is

• In ConfigData defaults have an empty target node and a 'defaults' node that has a template provides the actual defaults and that is heavily decorated with the ( &default ) marker.
• Have a rule with the value `(( merge( target, *defaults ) ))

config.zip

[Skarlso]

We already have an existing patch merge strategy option to handle large and complex cases for configuration.

[Skarlso]

Instead of configRef define a patchStrategicMergeRef that points to an exchange of complex values with a target and a path. The result will be merged based on kustomize merging strategy.

[dee0sap]

Believe this case has been fixed with the switch to using yqlib for merging the defaults and the config values.
That said it would be best to add a unit test that confirms it prior to closing this.

[Skarlso]

I'll add unit tests for these cases.

[Skarlso]

This PR now includes tests for these scenarios because without ocm v0.10.0 these don't work. open-component-model/ocm-controller#425

[Skarlso]

This should now have been fixed.