Pulumi adds Terraform state, native modules, and first-class HCL

Pulumi announced a three-part Terraform and OpenTofu interoperability release on August 4. The product post makes Pulumi Cloud’s Terraform state backend generally available, adds native Terraform-module consumption to Pulumi programs, and promotes HCL to a first-class Pulumi language.

Existing estates gain multiple entry points

Terraform and OpenTofu teams can retain their CLI workflow while moving state to Pulumi Cloud. New Terraform stacks run plans and applies remotely by default, and teams can configure manual approval before apply. Pulumi describes those state-backed stacks as first-class Cloud objects with access controls, policy evaluation, and deployment configuration.

Pulumi programs in any supported language can also import Terraform modules without translating the module first. The Pulumi Cloud private registry can host those modules alongside Pulumi packages, allowing the same module to serve Terraform and Pulumi consumers. Separately, HCL is now generally available for Pulumi IaC; the company says its syntax is compatible with OpenTofu and connects to Pulumi’s provider ecosystem through the Terraform bridge.

Interoperability still needs a zero-diff proof

A team should choose one boundary at a time. For a state-backend move, preserve a backup, test locking and failure recovery, and require the first remote plan to show no unintended changes. For module reuse, exercise provider constraints, outputs, sensitive values, and lifecycle behavior from both engines. For HCL, run the existing test suite and compare plans before applying.

The release reduces the need for a wholesale rewrite, but it also creates more valid operating combinations. Platform owners need a clear record of which engine, backend, registry, and execution environment owns each stack. That inventory makes mixed estates manageable and provides a rollback path when an interoperability edge case appears.