Add Variable Hierarchy to GitOpsConfig CR about eunomia HOT 6 CLOSED

Also need the ability to pass a blob of structured data in the GitOpsConfig spec to specify the hierarchy. This is an alternative to a list of variables.

from eunomia.

Came across this project that might help us merge the yaml files with the parameters: https://github.com/imdario/mergo

from eunomia.

I did some more research and this might already be directly supported in helm. We have to test it out: helm/helm#3486
Otherwise there's actually a plugin for helm to leverage hiera, which might be even more desired: https://github.com/cststack/k8comp

from eunomia.

Here's another approach, which would simply be a different templating engine: https://github.com/deepmind/kapitan

from eunomia.

I'm wondering if we should stick with the original idea and simply make parameter source a list with a defined priority. We would simply use yq to merge the files in the specified order. This way the hierarchy can span repos.

from eunomia.

The initial, but not final implementation was created as part of #156. Additional work is needed to make the hierarchy feature GA.

from eunomia.