3 ms·
I’m in the decision process around this stuff right now and would be curious if you have any more opinions around the two tools.
by klysm 4y ago
I’m in the decision process around this stuff right now and would be curious if you have any more opinions around the two tools.
- candiddevmike 4y agoPulumi was a one trick pony that never figured out a way to differentiate themselves before HashiCorp caved and delivered a Terraform CDK (Terraform for the longest time was extremely hard to use programmatically, you basically had to wrap the binary, you couldn't import a lot of the underlying Go code directly) (aside: HashiCorp still does this with Consul and friends, very annoying and has clear intentions on why). I would master Terraform modules with HCL before reaching for a CDK (or Pulumi). You may find you don't need anything more, or you'll figure out why you need those things instead. Plan your automation journey with the end user in mind but not an immediate goal, service your own needs first and eventually build out tooling _designed for them_.
- mountainriver 4y agoTerraform CDK has terrible UX compared to Pulumi
- cnunciato 4y agoReally? Why? Trying something new before becoming a "master" in something similar seems like a totally reasonable concept to me. I work on Pulumi, and even I don't actively discourage people from trying its alternatives. Use what makes you happy, I say.
- moltar 4y agoIf you are all in AWS then strong vote for AWS CDK. If you need other cloud providers, then perhaps check CDKTF as well. But also nothing wrong with using both. Just not on the same stack or sub system. TF also has other than cloud types of providers, which is interesting. Such as GitHub provider. Or Google Workplace.