jsonnet

Same as Jsonnet but it's only a small part of the picture. For someone who use JSON, I expect the adoption of CUE to be incremental but in reality I need to use CUE's own syntax to get the value out of it. Jsonnet was was closer to to the mindset that I have with that respect. Some context: https://github.com/google/jsonnet/issues/605#issuecomment-72...

They also have https://github.com/google/jsonnet and https://cue.googlesource.com/cue.

> There's nothing in Terraform that couldn't just be YAML with some semantics (like Ansible which I find much more approachable) One secret of Terraform is that you can define resources with JSON instead of HCL (https://www.terraform.io/docs/configuration/syntax-json.html). The catch is that all the interpolation and iteration stuff is implemented in HCL, so if you use JSON, you probably want something else to do that. But, eg, Jsonnet works beautifully for that kind of thing: https://github.com/google/jsonnet/blob/master/examples/terra...

How many folks are familiar with http://jsonnet.org/ - there are two implementations: - One in go - https://github.com/google/go-jsonnet - One in C++ - https://github.com/google/jsonnet AFAIK, ksonnet is the primary user - https://ksonnet.io/ - which to any ex-googler be the more familiar way of dealing with the borg configs. HJSon seems nice, as once in a while how to put a comment in JSON comes, and everyone starts bike-shedding their favourite solution, that leaves lots questions... of compatibility. For example, we tend to use "_comment": "", but I know that's bound to break somewhere, soon or later. There is also https://json5.org/

What you're describing here is remarkably similar to Jsonnet in syntax and style. Jsonnet is quite nice, imho! http://jsonnet.org/ https://github.com/google/jsonnet

[OP here] Another goal here is to have something that is easy to embed/repurpose. ruby is pretty heavyweight from that point of view. While jsonnet is a C program right now (https://github.com/google/jsonnet) we are looking at picking up work on a go port so it is easier to integrate with the kubernetes universe.

FWIW, the name is quite similar to https://github.com/google/jsonnet

An alternative is to use Jsonnet [0] (a JSON/YAML templating language). You can define an inheritance relationship, where your template inherits pretty much everything EXCEPT the environment variables. Or the jsonnet cli lets you specify variables to be replaced in the template. There's some kubernetes flavored examples in [1]. [0] http://jsonnet.org/ [1] https://github.com/google/jsonnet/tree/master/case_studies/k...

http://flabbergast.org/ is the closest, and in a similar vein you'd have https://github.com/google/jsonnet and then Nix. Configuration management is a very different thing to what most of ansible/chef/puppet/salt are commonly used for - it's possible to do it but it's a bit of an uphill battle. The core problem of config management is not pushing out things, but rather how do you represent configs with their myriad of interacting multi-level exceptions while also allowing tens/hundreds/thousands of operational changes to be ongoing at the same time. Ansible for example is good for about 3-4 levels of exceptions, which isn't that much considering region and environment (dev vs prod) are two of those.