Infrastructure as Code, Not Infrastructure as Files

Re:Infrastructure as Code, Not Infrastructure as Files by _frkl on Thursday October 17, 2019 @02:11AM (#21279364)

Neat, didnt know about CUE, this looks very interesting. Im working on my own wrapper framework (that can also do IaC, but not exclusively), and it supports optional input type specification and validation, to a point. Wish i had known about CUE when I started...

Ended up with a few of the features you mentioned, but not as nicely designed than CUE seems to be, esp. the data injection... Maybe another rewrite is in order... sigh

[ Parent | on HN ]

Re:Infrastructure as Code, Not Infrastructure as Files by Cedricgc on Thursday October 17, 2019 @03:44PM (#21285667)

I highly recommend using CUE for the configuration part. I may not have mentioned this, but CUE is a superset of JSON, You can write the config in CUE then compile the config into a final unified JSON file to be fed into another system. You can separate the orchestration and configuration of a system through an actual data transport system.

[ Parent | on HN ]