About this video
What You'll Learn
- Explains how Terraform CDK was archived without any deprecation window.
- Shows why download counts contradict HashiCorp's product-market-fit explanation.
- Argues the real issue was enterprise revenue, not community adoption.
HashiCorp, an IBM company, archived the Terraform CDK on December 10 with no deprecation window, blaming "product market fit" despite roughly half a million monthly downloads. The synth-to-HCL migration path misses why people picked CDKTF in the first place.
Full transcript
Generated from the English captions. Timestamps jump the player to that moment.
Read the full transcript
0:00 Alright. Here we go. Another one bites the dust. RIP Terraform CDK. Terraform CDK has been archived. As of yesterday, December 10, with all of zero minutes notice, the cloud development kit for Terraform is officially dead. HashiCorp, an IBM company, has archived the Terraform CDK repository. HashiCorp, an IBM company, has archived the repo. It's gone, done, read only. So you should not, I hope not, will be using Terraform CDK anymore. And let's just talk about HashiCorp, an IBM company. Why does this have to be everywhere? It's like whenever I read X, a company formerly known as Twitter,
0:40 it's annoying and it's bullshit. They put it everywhere now. It's like a stamp of ownership on everything for HashiCorp. And HashiCorp, an IBM company, didn't just stop working on the cloud development kit for Terraform. They've buried it with zero warning. No deprecation window. Just an archive and good luck. So sorry to anyone running this in production. I'm running this in production. Let's talk about the reasons. And honestly, this is where they insult all of our intelligence in one single go. They said, and I'll quote, they did not find product market fit at scale. Fuck off.
1:21 Look at the numbers. 250,000 weekly downloads on NPM, a quarter of a million downloads every single week. There's another 140 ks downloads per week on the CLI and that's just JavaScript and TypeScript, there's also Python and Go. Those numbers aren't quite as easy to get a hold of. No. Actually, it's the Go numbers that are hard to get, but the Python numbers are freely available on the PyPI website. And if you are curious how many downloads there have been in the last month for a CDKTF, it's only a cool half mil, you know. Barely a user base.
1:01:58 Certainly not a community. And if that isn't a fit, then half of the projects in the CNCF landscape are dead by default. Sorry, folks. You don't kill a project with, guesstimate, a million users every single month because nobody likes it or it doesn't have product market fit. You kill it because it's not increasing your profit margin. It's not selling enterprise licenses. But don't worry. HashiCorp, an IBM company, has given us a migration path. You can synthesize all of your Terraform, TypeScript, Python, and Go to HCL. Assuming assuming you're not actually doing anything useful in that code in the first place to
1:02:38 warn adopting the program in the fucking first place. Of course, this is not gonna work for most people. They're using Terraform CDK because they wanted infrastructure as code, not infrastructure as JSON. So this just proves that HashiCorp, an IBM company, never gonna get old saying that, proves that they just don't understand why people were using the tool in the first place. I didn't use Terraform CDK to not learn HCL. I know how to write HCL. I know its limitations and I know it doesn't work for me. I used code for composition, abstractions, classes, inheritance, NPM,
1:03:12 PyPI, building shareable modules that aren't Terraform modules because nobody likes using Terraform modules. No. It's not a migration path. It is a dump on all of our heads that trusted HashiCorp, an IBM company for so long. The logic gone. My code is dead. <v Speaker 05:03: 01: 01: 01: 01: was replaced with Sutter's code is dead. 01: 0: 01: 0: 01: 01: 01: 3.
Technologies featured
Stay ahead in cloud native
Tutorials, deep dives, and curated events. No fluff.
Comments