Petr Michalec

This might be nice solution https://docs.saltproject.io/salt/user-guide/en/latest/topics/jinja.html#using-renderer-pipes shebang like ``` #!jinja|yaml ```` single files could be rendered/interpolated multiple times, easy to implement, no config (or dedicated file) needed.

> @epcim I like that idea and will take it into account when/if I start working on multi template engine support. when you suggest right place, I could have a...

Shebang in file header, as comment  is soft and better imo. Its like filter fn for whole file. That kluctl may understand but dont break other tools. Imo I have...

For a record, jinja2 in manifests is sometimes really helpful. Though as gotempl libraries improve the difference is not big. @codablock could you draft/design what way you would like to...

vars, are updated on each deployment item, which usually happen multiple times during rendering. would you like to print them each time the "folder" is processed just for debugging purposes?...

Just cross-linking the idea with shebang, that would either allow to disable rendering, etc. per file etc.. https://github.com/kluctl/kluctl/issues/268#issuecomment-1491923874

I have the same issue, surprisingly restart of fluend works for a while. I would appreciate a guidance as well. It's not clear what buffer is over and how to...

> Strict YAML parsing is mandatory as otherwise unknown fields are ignored, which can easily lead to unexpected behaviour, e.g. due to simple typos. I agree. Sorry I was not...

Would the MR be accepted if implemented only for Vars? Any other idea how to merge yaml structures with templating (well I use multiple vars, overrides - but the problem...

> Hmm, I'm pretty sure that strict loading for vars has no effect on unknown fields (because it's schemaless), but only on duplicated fields. I wonder why you even end...