5 ms·
All of HashiCorp's products have splendid UX — what are you on about? Have you actually used their other products aside from Terraform, which I'm assuming you'r
by Axsuul 4y ago
All of HashiCorp's products have splendid UX — what are you on about? Have you actually used their other products aside from Terraform, which I'm assuming you're referring to?
- datatrashfire 4y agoI don't understand why some people hate teraform so much.
- lapser 4y agoBecause it sucks. It has all the quirks and a whole lot of mess. That's terraform. Terraform Enterprise and Cloud must have been developed as a fuck you to enterprises, because it absolutely sucks. I work with them daily, and have done so for 4 years now. It still sucks. Unfortunately it's (Terraform, not TFE/TFC) the best in its class, and quite frankly I'm not smart to solve its issues.
- cube2222 4y agoIf you're having a bad time with TFC/TFE, make sure to check out Spacelift[0]. We're striving to build a product that's both highly customizable and has a good UX, improving on many of the pain points. The migration path is straightforward and it'd be great to hear what you think about it! [0]: https://spacelift.io https://spacelift.io Disclaimer: Software Engineer at Spacelift
- lapser 4y agoI have checked it out. Also checked out Scalr and some other one that I can't remember the name of. Issue isn't finding an alternative, it's convincing the team to move away from TFE and TFC.
- deleted 4y ago[deleted]
- thayne 4y agoTerraform is great... until you hit one of it's many limitations, or run into a bug in a provider that really ruins your day. Plenty of people probably never run into those problems. But if you do, it's pretty terrible. To be fair, there isn't really anything better. Pulumi and CDK address some of the limitations by using a "real" programming language, but introduce different issues. And bugs in providers are probably unavoidable, and are partly the fault of poor APIs from cloud providers.
- throwaway787544 4y agoAgreed. And nobody tries to replace it because nobody could replace all those providers without an army of engineers. And nobody is going to use a new project that only implements one or two APIs.
- sdnas211 4y ago> run into a bug in a provider that really ruins your day Most of these problems I encounter aren't even down to hashi themselves. The GCP provider consumes from google's magic modules repo, which is often out of sync with the GCP API. Or in plenty of cases, it is in sync, but the API does not expose features in the same way as the console.