Pulumi's HCL Support Reaches General Availability, Bridging IaC Ecosystems for Enhanced Flexibility

Pulumi has announced the general availability of its comprehensive support for HashiCorp Configuration Language (HCL), including the ability to manage existing Terraform state files and convert Terraform modules into cross-language components. This strategic move, which had been in private beta since January 2026, was officially rolled out in August 2026, as detailed in a blog post by Daniel Perlovsky titled “Bring Your Terraform Estate Into the Agentic Era.” This development is highly significant for practitioners in the infrastructure-as-code (IaC) space. It directly addresses a major hurdle for many organizations considering a transition to Pulumi: the existing investment in Terraform and the preference for HCL's declarative syntax. By allowing teams to continue writing HCL, manage their Terraform state, and even reuse Terraform modules within the Pulumi ecosystem, Pulumi is effectively removing a significant barrier to adoption. This matters because it enables a more gradual and less disruptive path to modernization, allowing teams to incrementally adopt Pulumi's benefits, such as its support for general-purpose programming languages, remote execution capabilities, and AI-powered infrastructure agents like Pulumi Neo. This move by Pulumi fits squarely within the broader trend of convergence and interoperability in the cloud and DevOps landscape. As infrastructure complexity grows, driven by multi-cloud strategies and the increasing adoption of AI, there's a clear demand for tools that can abstract away underlying differences and provide a unified management plane. The ability to seamlessly integrate with existing Terraform assets while offering advanced features aligns with the industry's push towards platform engineering and internal developer platforms (IDPs). These platforms aim to provide developers with self-service capabilities while maintaining consistency and control, and a tool that can bridge different IaC paradigms is crucial for achieving this. The trend of AI-driven infrastructure management, exemplified by Pulumi Neo, further underscores the need for flexible and extensible IaC platforms that can integrate with intelligent automation. In practice, this means that organizations previously hesitant to explore Pulumi due to their Terraform commitments now have a compelling reason to re-evaluate. Teams can start by importing their existing Terraform state and gradually introduce Pulumi programs written in HCL or other supported languages. This allows them to leverage Pulumi's advanced features, such as policy enforcement, AI-driven code reviews, and a unified control plane, without a complete overhaul. For greenfield projects, the choice between Terraform/OpenTofu and Pulumi becomes less about language preference and more about the desired operational model and the long-term vision for infrastructure automation. Practitioners should consider how this newfound interoperability can streamline their workflows, reduce technical debt, and accelerate their adoption of more advanced cloud engineering practices.