Pulumi lets teams define cloud infrastructure using general-purpose languages (TypeScript, Python, Go, C#, Java, YAML) instead of HCL, bringing familiar IDE tooling, package managers, and test frameworks to infrastructure code. Key advantages over Terraform include: aliases for safe refactoring without surprise resource replacements, first-class encrypted secrets that propagate through outputs, explicit lifecycle controls (protect, retainOnDelete, deleteBeforeReplace, replaceOnChanges), stack-based environment modeling with per-stack config and cross-stack references, unit/integration testing with normal language test runners, and explicit provider resource wiring for multi-region/multi-account setups. Incremental migration from Terraform is supported via pulumi import and Terraform provider interoperability. The post is candid about limitations: Pulumi does not eliminate cloud API eventual consistency, provider bugs, drift, or preview-time unknowns — those still require engineering discipline.
