Pulumi vs. Terraform – Hypergrowth in the Valley
medium.com
medium.com
I'm not a huge fan of Hashicorp's HCL---I'd prefer something more flexible and powerful like Jsonnet or Dhall---but I'm a believer in DSLs in general and that the right DSL is the best solution here. Cloud configuration is really a very different problem domain from general-purpose programming and it seems to me pretty self-evident that a well-designed DSL can make us more productive in this space and produce more readable configurations than a general-purpose programming language.
There are significant issues with it - terrible stability and reliability between version upgrades, its constant desire to tear down entire sets of resources and regenerate them when no change has occurred etc.
I assume these issues stem from the fact that pulumi's azure providers are generated directly from the terraform providers and practically nobody ever uses those.
The only reason I'm mentioning it is that I only ever see pulumi described in glowing reports of success whereas for us it's beginning to seem like a mistake ever using it in the first place.
Since everything is open I can always fork/maintain it myself.
I’ve never had that situation in Pulumi yet.
It’s just a matter of getting everyone else on the bandwagon. As long as everyone in our team uses the same it works fine.