3 ms·
I myself would love to see more usage of HCL... after writing a lot of Terraform configurations, it feels so much nicer for me than any JSON or YAML/Helm config
by chrizel 6y ago
I myself would love to see more usage of HCL... after writing a lot of Terraform configurations, it feels so much nicer for me than any JSON or YAML/Helm configuration I have written to this day. We should agree on some kind of HCL-based industry standard and leave all these workarounds via JSON/YAML behind us... e.g. doing Helm logic with these Go templates just looks like a step backwards after writing Terraform HCL code for the last 2-3 years.
I understand JSON as a simple interchange format between systems, and is here to stay, but I don't understand all this YAML stuff, with all its quirks, from the K8s/DevOps people, when we have the much nicer HCL...
For anyone not used to HCL: https://github.com/hashicorp/hcl https://github.com/hashicorp/hcl
- RulerOf 6y agoThe thing I dislike about YAML is how unwieldy it gets and how quickly that happens. "Simple" YAML files tend to be half a dozen pages long. HCL is more information-dense.
- sand_castles 6y agohow is HCL better than YAML ? people can misuse HCL too, YAML misuse is not uncommon.
- cbushko 6y agoI too prefer HCL to YAML and especially to helm templating. Loops and conditionals in HCL could still use some real work though. They are still clunky to work with.
- Aeolun 6y agoI liked HCL until I did some infra writing in Pulumi Typescript, and now I just want all my config files to be code.