Máté Őry
Máté Őry
Not an issue, nested lists do work correctly. Given that the missing spaces are added, you have nested lists of single-key maps: `{"part1":[{"level1":[{"level2":[{"level3":{"key1":"value1","key2":"value2"}}]}]}]}`. ``` cfg, err := config.ParseYaml("bar: [[[foo]]]") fmt.Println(err,...
cc and thanks @fekete-robert
it seems like we need this one too to make it work k3s-io/klipper-helm#46
We've workarounded this by rearranging the manifest templates in a way that all variable substitutions come before the parts that need escaping, and adding a comment like `# hack: $${}`...
I'd implement the env var only. It'd be inconsistent when banzai login would write these to the config while all other commands handle it just like a config.
* "If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used." * Load config from `$BANZAICONFIG` file, or from the first directory existing of...
I would stick to using `$HOME/.config/banzai` only if XDG_CONFIG_HOME is not set.
> That's exactly what the above means. (And that's why I emphasized the order) Not really. We shouldn't check $HOME/.config/banzai if a different XDG_CONFIG_HOME is set, but there is no...
> Why not? Because the referenced xdg standard defines it this way.
> No. It only says what should be the fallback if the relevant env var is not defined. Nothing says we can't use it otherwise. Yes, and that's the only...