Add a way to provide default vars layer for libraries?

[funbiscuit]

Currently if we include kluctl library in our deployment, we can provide some vars. Like so (for example assume library is somewhere locally):

deployments:
  - include: /path/to/lib
    vars:
      - file: lib-values.yml

Contents of lib-values.yml:

deployAwesome: true

And assume in library deployment we have something like this:

 vars:
    - file: defaults.yml

Contents of defaults.yml:

deployAwesome: false

Since defaults.yml is included later, it will overwrite all values that we passed to library. Which makes vars field somewhat useless. I know that args is preferred way to work with libraries, but it would be very great to provide vars and overwrite anything that is present in library deployments. Since libraries are meant to be used outside and we should be able to overwrite their configuration.

Maybe we could add vars on library level? And then all passed vars will overwrite them. Or some other way to include vars in library with lowest priority so passed vars will overwrite them.

So this is more like a feature request, but I wanted to ask what do you think before opening actual issue.

[codablock]

Can you check if https://kluctl.io/docs/kluctl/templating/variable-sources/#nooverride already solves your requirement?

[funbiscuit]

Yes, that's exactly what I wanted! Thanks a lot, I somehow overlooked that in documentation.

[codablock]

Great. Using kluctl libraries properly with things like defaults is something I planned to write down in the form of a recipe, but lacked time so far. I'm also happy with contributions in that regard 🙃

[funbiscuit]

Closing as proposed feature already exists