2 ms·
For me the target is mostly verbose YAML configuration of existing software (which I can now emit from an in-memory object instead of templating and having to r
by q3k 7y ago
For me the target is mostly verbose YAML configuration of existing software (which I can now emit from an in-memory object instead of templating and having to remember all the YAML quirks) and k8s manifests. Especially when I have to stamp the same piece of software multiple times in multiple deployments (environments/regions/etc).
For instance: I just brought up a new Factorio game server yesterday, just by adding a single line to my jsonnet configuration machinery: https://gerrit.hackerspace.pl/c/hscloud/+/246 https://gerrit.hackerspace.pl/c/hscloud/+/246 . This in turn brought up a bunch of new k8s resources, including some persistent volumes, a deployment, and a loadbalancer service, after running a single `kubecfg update` command.
- jevgeni 7y agoI agree, that YAML is usually a mistake. In your scenario, it's more like provisioning of infrastructure and in that case - configuration is the code, so I can see where you are coming from. I mostly write financial software so the use case is usually closer to classical single machine applications. And in that case, I prefer simple TOML.