12 ms·
One reason is because TF supports many clouds and people like having skills that are not vendor specific
by verdverm 5y ago
One reason is because TF supports many clouds and people like having skills that are not vendor specific
- hckr1292 5y agoHalf true. The true half is that terraform will work out of the box with basically all clouds and many saas vendors. The untrue half is that terraform does nothing to abstract away the underlying vendor. You cant treat gcp VMs the same as aws EC2 instances. You do get to reuse HCL.
- verdverm 5y agotrue, but the tooling and workflow remains the same. Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config. I'm exploring using CUE (https://cuelang.org https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer