→ Back to Home
Pulumi

Pulumi Embraces HCL and Terraform State, Signaling a Unified IaC Future

Pulumi has made a significant strategic shift by announcing native support for HashiCorp Configuration Language (HCL) and the ability for Pulumi Cloud to serve as a state backend for both Terraform and OpenTofu. This development, with general availability expected in Q1 2026, allows engineering teams to execute HCL directly through the Pulumi engine and manage Terraform state within Pulumi Cloud. This is a notable departure for Pulumi, which has historically championed general-purpose programming languages for IaC. This move is particularly impactful for practitioners navigating the complex and often fragmented Infrastructure as Code ecosystem. It matters because it offers a pragmatic solution to the challenges of multi-tool environments and the operational friction associated with migrating between IaC platforms. By embracing HCL, Pulumi acknowledges the substantial existing investments in Terraform and provides a bridge for organizations to leverage Pulumi's advanced features, such as its AI engineering agent Neo, without a complete rewrite of their infrastructure code. This directly benefits platform teams and DevOps engineers seeking to streamline their operations and improve governance across diverse IaC estates. This announcement fits within a broader trend in cloud and DevOps towards consolidation, abstraction, and AI-driven automation. The IaC landscape has seen considerable upheaval, particularly following HashiCorp's licensing changes and the subsequent rise of OpenTofu. Organizations are increasingly looking for solutions that offer flexibility, reduce vendor lock-in, and integrate seamlessly with their existing CI/CD pipelines. Pulumi's expansion into HCL support and Terraform state management is a direct response to this demand, positioning itself as a more universal control plane for infrastructure. This aligns with the growing emphasis on internal developer platforms (IDPs) and the need for unified visibility and governance across heterogeneous cloud environments. In practice, this means several things for practitioners. Firstly, teams with existing Terraform or OpenTofu codebases can now consider integrating Pulumi Cloud for state management, gaining access to its governance, visibility, and AI capabilities without abandoning their current IaC language. Secondly, for organizations contemplating a shift from Terraform, Pulumi offers a less disruptive migration path, allowing for a gradual transition or even a polyglot approach where different teams can use their preferred language. Pulumi also introduced a financial 'escape hatch' program, offering credits equivalent to remaining HashiCorp contract values, further easing potential transitions. This development underscores the importance of evaluating IaC tools not just on their native language capabilities, but on their ability to integrate and manage diverse infrastructure landscapes.
#iac#terraform#hcl#pulumi cloud#devops#multi-cloud
Read original source