Pulumi's HCL Support: Unifying IaC Workflows for Terraform and OpenTofu Users

A recent workshop announcement from Pulumi, scheduled for today, August 17, 2026, highlights the general availability of comprehensive support for HashiCorp Configuration Language (HCL) within the Pulumi ecosystem. This development signifies Pulumi's commitment to enabling organizations to manage their entire Infrastructure as Code (IaC) estate, including existing Terraform and OpenTofu configurations, directly through its platform. The workshop, titled "Pulumi for All Your IaC: Including Terraform and HCL," will demonstrate how practitioners can integrate their existing Terraform workloads with Pulumi Cloud, reuse Terraform modules within new Pulumi programs, and author new infrastructure using HCL as a fully OpenTofu-compatible language. While the workshop is today's news, the underlying general availability of HCL support, alongside Terraform state management and cross-language module sharing, was officially announced on August 4, 2026. This integration is a significant development for the IaC landscape, directly impacting teams grappling with heterogeneous infrastructure environments. It matters because it removes a major barrier for organizations considering Pulumi but constrained by substantial existing investments in Terraform or OpenTofu. Previously, migrating to Pulumi often implied a significant refactoring effort to translate HCL into one of Pulumi's supported general-purpose programming languages. Now, teams can adopt Pulumi incrementally, benefiting from its unified control plane, policy-as-code capabilities, and advanced features like Pulumi Neo for AI-powered code reviews, all while preserving their existing HCL codebases. This flexibility is particularly valuable for large enterprises and platform teams that need to support a mix of legacy and modern IaC practices. This move by Pulumi fits squarely within the broader trend of IaC platforms striving for greater interoperability and reduced vendor lock-in. The industry has seen a growing demand for tools that can bridge different IaC paradigms, especially in the wake of HashiCorp's licensing changes, which prompted many users to explore alternatives like OpenTofu and other IaC solutions. Pulumi's strategy here is to position itself as a universal IaC control plane, capable of managing infrastructure defined in various languages and tools. This aligns with the concept of a "platform engineering" approach, where central teams provide a cohesive set of tools and services that abstract away underlying complexities, allowing product teams to choose their preferred IaC language without sacrificing governance or operational consistency. In practice, this means practitioners should evaluate Pulumi not just as an alternative to Terraform, but as a potential unifying layer for their entire IaC strategy. Teams can now leverage their existing HCL expertise and modules, integrating them into a Pulumi workflow to gain benefits like enhanced state management in Pulumi Cloud, cross-language component sharing, and robust policy enforcement. This could lead to smoother transitions for organizations looking to modernize their IaC practices or consolidate tooling. For those already using Pulumi, it opens up the possibility of incorporating a broader range of community-contributed Terraform modules directly. However, practitioners should still understand the nuances of how Pulumi interprets and executes HCL, as detailed in Pulumi's engineering blogs on compatibility testing, to ensure seamless integration and predictable behavior.