IBM HashiCorp ‘Sunsets’ Terraform’s External Language Support

Going forward, when you run IBM‘s Terraform Infrastructure as Code (IaC) software, you will have one language to write your configurations: the HashiCorp Configuration Language (HCL). On Monday, HashiCorp, an IBM company, announced that it will no longer support the Terraform Cloud Development Kit (CDK or CDKTF). Although the existing code will remain available in a GitHub archive, HashiCorp will no longer maintain or update the code, leaving it all but unusable for enterprises. “Unfortunately, Terraform CDK did not find product-market fit at scale. HashiCorp, an IBM Company, has chosen to focus its investments on Terraform core and its broader ecosystem,” a note on the site read. The CDK itself is licensed under the Mozilla Public License (MPL), so users are free to fork the software itself, IBM suggested. The company, however, is encouraging users to use HCL, which was developed by HashiCorp and licensed under the Mozilla Public License (MPL), originally designed for the software. Terraform’s Rocky History Originally released in 2014 by HashiCorp, Terraform is software that allows administrators to automate the deployment of IT infrastructure, either in the cloud or on premises, through the use of scripts and a set of Terraform commands such as terraform init, terraform plan and terraform apply. The output is rendered as JSON. Over time, Terraform has become the most popular software for automated IT deployment, especially in the cloud native community. In 2023, HashiCorp switched the Terraform license from open source to a Business Source License, which spurred a user-based open source fork of the software, called OpenTofu, that was adopted by the Linux Foundation and, later, by the Cloud Native Computing Foundation (CNCF). In 2024, IBM announced it was acquiring HashiCorp and finalized the purchase earlier this year. Terraform CDK Migration Plans Despite a call to open source the CDK, IBM is encouraging current users to adopt the HCL if they are not already doing so. “If you are not using AWS CDK, we highly recommend migrating to standard Terraform and HCL for long-term support and ecosystem alignment,” the company asserted. Terraform users with .tf files created under the CDK can convert them to HCL with the following command: cdktf synth --hcl Those using CDTF on Amazon Web Services infrastructure can also use AWS’ own CDK. The Limits of IaC Overall, the Infrastructure as Code user base appears to be chafing from the limits of IaC. As a result, many alternative approaches to Terraform have popped up in the last few years, including Adam Jacob’s System Initiative and Formae from Platform Engineering Labs. They point to how HCL has its limits, especially for highly scalable environments. A declarative configuration language, HCL is limited in offering advanced programming constructs, and many resulting workarounds have resulted in obtuse code. Tooling is limited as well. The advantage that the CDKTF brought to users was that it allowed them to detail deployment instructions through their own favorite programming language rather than HCL. CDKTF supported TypeScript, Python, C# and the Go programming language. This is also the approach that Terraform competitor Pulumi has staked out, namely the ability to provision infrastructure in any one of a number of programming languages. Yet, there has also been considerable debate around whether a general-purpose programming language is better than a domain-specific language. Terraform’s users are administrators, not programmers, as critics have pointed out. Community Reaction Nonetheless, many of those in the IaC community took the news hard. Kubernetes expert David Flanagan noted that the development kit has gotten over 140,000 downloads per week for TypeScript alone, with similar numbers in other language communities. So clearly, the CDKTF is still highly used by the community, he argued. Fuck you, Hashicorp … an IBM Company. pic.twitter.com/h1EicnT3pL — David Flanagan (@rawkode), Dec. 11, 2025 “You don’t kill a project with [an estimated] million users every single month because nobody likes it or it doesn’t have a ‘market fit.’ You kill it because it is not increasing your profit margin, it is not selling enterprise licenses,” Flanagan said in a short video. To be fair, IBM has a long history of buying open source-based companies, and keeping the open source licensing intact, including the Linux-based Red Hat, the Cassandra-focused Datastax and, most recently, the Kafka-based Confluent. (There’s been no word, however, on whether IBM would revert the Terraform license back to open source.) Flanagan went on to note that people are probably using the CDKTF because they require the additional programming capabilities. “It’s called Infrastructure as Code, not Infrastructure as JSON,” he quipped. Site reliability engineer Liz Fong-Jones offered a more measured response. “To be more gentle about this, HashiCorp has decided to stop trying to compete with Pulumi with language-native APIs; they’re all in on HCL as the only way to work with Terraform,” Fong-Jones wrote on BlueSky. Do We Need a Programming Language for IaC? In fact, others think this may not be a bad idea. Platform Engineering Labs’ Co-Founder and CEO Pavlo Baron thought the IBM move made sense. “IBM is historically good at optimizing for the target buyer. This is rather a sign that nobody on the right side of the cycle wants to do full-blown programming. CDKs, and this includes the approach Pulumi takes, are exclusively for developers. Developers usually don’t operate infrastructure,” he wrote by email. “Serious operations happen on the right side of the cycle, though. Thus, the CDK is missing their target user and addresses the wrong one. So I understand and support the logic behind this move.” The post IBM HashiCorp ‘Sunsets’ Terraform’s External Language Support appeared first on The New Stack.