Quick summary

  • Pulumi has made Pulumi Cloud available as a Terraform backend and brought HCL in Pulumi IaC to general availability. For established Terraform teams, that creates a trial path to change operational layers without immediately rewriting infrastructure code.
  • State and execution workflows are often the hardest parts of a mature Terraform estate to change. Separating that operational decision from a language rewrite can reduce migration risk.
  • Pilot one non-critical workspace, preserve a state backup, and compare plans, access controls, and recovery behavior before broader adoption.

What happened

For many devops teams, the difficult part of modernizing a Terraform estate is not HCL syntax. It is the accumulated state, access controls, execution conventions, and failure-handling procedures around it. Pulumi is addressing that boundary by positioning Pulumi Cloud as a Terraform backend while making HCL in Pulumi IaC generally available.

The practical implication is not that every team must convert infrastructure into a programming language. In its announcement, Pulumi says existing IaC can be brought into Pulumi Cloud while teams continue to work with HCL.

What changes around Terraform state?

State is Terraform’s record connecting declared resources to real infrastructure. A backend or execution change can therefore affect planning, applying, collaboration, and incident response—not merely storage. Pulumi says its new support covers Terraform state, hosted modules, and remote execution, and its hands-on walkthrough connects those capabilities in a Pulumi Cloud workflow.

A platform engineer comparing two infrastructure change paths in a controlled cloud environment.
A platform engineer comparing two infrastructure change paths in a controlled cloud environment.

That is a useful evaluation surface, but not a guarantee that a particular repository will behave identically without testing. Providers, module conventions, state history, and organizational controls all matter.

Why this is more than a tool swap

The backend governs how state is managed and how runs are coordinated. The engine governs how configuration is evaluated and changes are performed. When both layers change, teams need to validate plan behavior, state locking, inputs, secrets, approvals, and recovery procedures together.

That distinction matters for platform teams. A successful syntax-level proof of concept is insufficient if an operator cannot reproduce the required access model or confidently recover from an interrupted run.

How to run a useful trial

  • Pick an isolated workspace rather than a business-critical shared foundation.
  • Back up state and compare plans from the current workflow and the proposed workflow on the same revision.
  • Exercise access policies, secret handling, state locking, and approval paths explicitly.
  • Test rollback and drift response before allowing production applies.

What to watch next

Pulumi describes HCL in Pulumi IaC and Pulumi Cloud as a Terraform backend as GA capabilities. That establishes a supported starting point, not an automatic migration decision. The important next evidence for each team is whether its own providers, modules, and operational controls preserve expected behavior.

In 5 Minutes

  • Pulumi Cloud is now positioned as a Terraform backend.
  • GA HCL support lets teams keep a familiar configuration language initially.
  • State and operating procedures must be tested together.
  • Start with a reversible pilot and plan comparison.

Sources

Why developers should care

State and execution workflows are often the hardest parts of a mature Terraform estate to change. Separating that operational decision from a language rewrite can reduce migration risk.

  1. 1Pilot one non-critical workspace, preserve a state backup, and compare plans, access controls, and recovery behavior before broader adoption.