Re:HashiCorp’s multi-product strategy
by throwaway787544 on Wednesday August 31, 2022 @08:06AM
(#32661090)
Agreed. 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.
> 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.
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.