This message was deleted.

We have this on the Pulumi website: https://www.pulumi.com/docs/intro/vs/terraform/

This could be useful, thanks Piers!

I don’t have a spreadsheet but I do have a few anecdotes I started importing a bunch of our GCP and kubernetes resources into Terraform, got stuck on not being able to create k8s custom resources (specifically managed certificates), and made the switch to pulumi. you can create managedcerts with tf now, but I’m very happy with the switch. I’m a big fan of Pulumi’s concepts of projects and stacks (and being able to import things from different projects, as long as the stacks are colocated, e.g. in the same gcs bucket) also, being able to type

if (environment === 'prod') { … }

to include or exclude certain resources in certain environments is a huge win for readability in our code. We have a few diagnostic tools (like Polaris) that only run in non-prod environments, and making that work ended up being pretty unreadable in the tf config – at least from what my unexperienced self managed to come up with. also also, I never managed to work around this annoying bug in tf https://github.com/hashicorp/terraform/issues/21702#issuecomment-525658662 which is still open a year and a half later also also also, being able to use typescript for the infrastructure (which is what we use for practically everything else in our monorepo with 50-ish packages) is a huge win. hcl looks simple but in my experience definitely takes some getting used to, and it acts as a barrier that prevents other developers from contributing. getting people used to typescript started with pulumi has been pretty easy in comparison, so I don’t have to be the only one touching infra-related code 🙂

Very useful, thank you kindly for this @broad-helmet-79436