There are quite a few of these things (Dahl, Jsonnet, etc).
and I've always thought it would be impossible to get a large enough team to learn them.<p>At a pervious organization I worked I wrote a Kubernetes manager (docker build + kube config generation + blue/green deploy) that was essentially TOML + Jinja (we we're a python shop). A django + pg + redis app would look like [1].<p>[1] <a href="https://gist.github.com/pnegahdar/1e90f42c1686009e1ff9392b797a6ed5" rel="nofollow">https://gist.github.com/pnegahdar/1e90f42c1686009e1ff9392b79...</a><p>There were definitely some limitations to doing this (some good, like reduced kubernetes surface) but in the end I think we got a large percent of the team writing kubernetes configs through cargo-culting while having generally sane defaults, environment isolation, etc.<p>I wonder how organizations get people to use these things in a broad way? I'd still be hesitant to write what was described above in something like jsonnet even though it would be much more semantically correct -- I can't imagine getting anyone outside of the ops team to use it!<p>Generally though, TOML works really well with templating languages (jinja, golang templates, etc) if you include some helper funcs. You can even pass the toml to itself on rendering til you hit a fixed point for references and such.