3 ms·

Man, I didn't think anyone would out yaml helm, but here we are not just templating invisibly scoped files (yaml), but also SQL within them? Looking forward to

Man, I didn't think anyone would out yaml helm, but here we are not just templating invisibly scoped files (yaml), but also SQL within them? Looking forward to the yaml confusion when helm/dbt both see their default "charts/" directory in the same repo, or the dbt chart is set as a config map so it can be updated without rolling a new version of the full app... helm_argo is already a nightmare rant aside, this does look super useful, and I do have CUE to help with the yamhell, but I may still prefer js/ts options so I can dynamically change the chart (like user clicking a dropdown for a different set of data). Sounds cool until the "dynamic" part of the chart shows it's limitations in crafting your ideal UX I'll definitely be taking this for a spin, gets at that unbundling and "I need a quick chart" situations

mollifier14 1mo ago
I don't quite understand the YAML hate from some people. I agree that Helm is messy, but it has a lot of coding like things in YAML and then it feel like dependencies just live randomly somewhere. For the most part our YAML files are self contained. Yes you can use ref() and also pull other files, but most of that is obvious in syntax. What we should do is to make sure our YAML is as easy to navigate as possible in various editors, especially VScode with the extension
- verdverm 1mo ago
  Or just use CUE, it's sooo much better, you can use it in conjunction with/extension to all the popular formats, get real schemas/imports/modules I discovered CUE after trying to do too much in yaml, after adding imports I had to step back and ask what I am I doing. It's super hacky, a real language is much better long-term in reliability and maintainability. DevOps seems to enjoy the pain, unsure why we continue to use messy tools. CUE is actually nice and fun to use before any comparisions to existing config formats.

mollifier14 1mo ago

I don't quite understand the YAML hate from some people. I agree that Helm is messy, but it has a lot of coding like things in YAML and then it feel like dependencies just live randomly somewhere. For the most part our YAML files are self contained. Yes you can use ref() and also pull other files, but most of that is obvious in syntax. What we should do is to make sure our YAML is as easy to navigate as possible in various editors, especially VScode with the extension

verdverm 1mo ago
Or just use CUE, it's sooo much better, you can use it in conjunction with/extension to all the popular formats, get real schemas/imports/modules I discovered CUE after trying to do too much in yaml, after adding imports I had to step back and ask what I am I doing. It's super hacky, a real language is much better long-term in reliability and maintainability. DevOps seems to enjoy the pain, unsure why we continue to use messy tools. CUE is actually nice and fun to use before any comparisions to existing config formats.