Strong agree. It’s also the absolute best at expressing really long documents of configuration/data.

I think that’s the way both Splunk and JFrog work – you generate or enter a password into the key field in a YAML file somewhere, start the service, and next time you come back the field’s been encrypted.

“A The Lord of the Rings Game”

I’m going to have a the stroke.

I can confirm both Pixels and Samsung phones have that feature (1/2/4 hours or indefinite). On my current phone (Samsung) you get the option by holding the DND button.

deleted by creator

Oh, it’s all still Kubernetes YAML. The difference is in how it’s represented. Helm Charts are packaged Golang templates of Kubernetes YAML, and as such have a whole lot of limitation since the only logic you can put into them is Golang template logic.

This is still Kubernetes YAML, but instead you write any program you want to return the YAML, as long as it fits in the sandbox, so it’s pretty open-ended. For example, as a stretch goal, I might add an engine to it that could recompile Helm Charts into Mistletoe Modules.

So Helm never fell short for me as an end user. As far as that goes, it’s near-perfect.

Where it does fall short is as a package writer. A package in Helm is just Kubernetes YAML that’s templated in Golang templates. As such, it gets very hard to any logic beyond the most basic, and projects that get larger get very unwieldy.

Hmm, what’s your idea for the OCI image format, e.g., how would it work? That might be worth looking into, too.

I mean, I get it, but there’s value in paying for support and updates, and it’s untenable for an organization to do that for free. I’m optimistic for software running under this model, I’d 1000% love to go back to the pay once per major version model, but “pay once forever” software leaves some unanswered questions.