4 ms·
Seen this at a couple companies and it doesn’t work well. The platform team becomes a bottleneck and the devs don’t want to have to deal with or learn the mess
by mountainriver 4y ago
Seen this at a couple companies and it doesn’t work well. The platform team becomes a bottleneck and the devs don’t want to have to deal with or learn the mess that is terraform.
It’s time for the ecosystem to move beyond the half baked config language known as HCL
- james_s_tayler 4y agoPulumi
- Too 4y agoWhat do you suggest instead?
- frederich 4y agoHave a look at GruCloud, an alternative to Terraform/Pulumi/CDK, which generates the infrastructure code automatically from a live infrastructure. Disclaimer, I am the author.
- Terretta 4y agoDisclaimer: a kind of disavowal, rejection of responsibility Disclosure: put hidden info forward, e.g. source of potential bias
- mountainriver 4y agoPulumi seems a lot more sane, trying to back all the complexity of infrastructure into a config language just doesn't add up at the end of the day. This is why we have general purpose languages. We could also probably use more abstractions similar to Pulumi, theres been talk on HN about storing all of the state for applications like this in the tags of the underlying cloud resources. There are some caveats with this approach, but it would provide a interesting tradeoffs