If you provision infrastructure at scale, you know the pain.
AWS, Azure, or GCP announces a massive new feature. Your development team wants to use it immediately. You go to implement it in your IaC pipelines, and... the Terraform provider doesn't support it yet.
Welcome to the "Gap of Grief"—the frustrating void in days between a cloud provider releasing a feature and Terraform actually supporting it.
To help architects stop guessing and start measuring this gap, we built the Terraform Feature Lag Tracker over at Rack2Cloud. It’s a dynamic tool that tracks the exact release gap in days across major cloud providers.
We put it out into the wild. And that is when the best part of building in public happened.
The Community Stress Test
We didn't do a massive launch. But shortly after it went live, Khalid Hosein, a Cloud Architect, found the tool and organically shared it with his network on LinkedIn.
He liked the core concept, but he immediately identified a UX blind spot we had missed:
"This tool tracks the gap in days between when a cloud releases a new feature and it's available in Terraform... Only thing missing is a filter that narrows it down to only the unsupported features."
He was 100% right. Our initial version was displaying the data, but it was burying the lede. Architects don't just want to see the lag time of supported features; they need a rapid audit of what is currently breaking their deployment plans.
The Refactor: Surfacing the "Gap of Grief"
Instead of throwing his suggestion into a "someday" backlog, we went straight back to the code.
Within a few hours, we refactored the backend logic. We re-engineered the tracker to prioritize and hard-code the "Not Supported" features right to the top of the stack.
Instead of just being a historical log, the tool instantly transformed into a live, actionable audit of the exact features you can't use yet. We replied to Khalid, let him know his feedback directly drove the refactor, and shipped the update.
Why We Build in Public
When you are deep in the code building a tool, you often lose the perspective of the end-user. You build for completion, not always for immediate utility.
This interaction was a perfect reminder of why engineering shouldn't happen in a vacuum. Community feedback—especially from experienced architects who are living the pain points you are trying to solve—is the most valuable telemetry you can get.
Check the Drift
If you want to see exactly how far behind your Terraform providers are right now, you can check the live tracker here:
👉 Live Terraform Feature Lag Tracker
Take it for a spin. If you spot another blind spot, or if you have a feature request that would make your Day 2 operations easier, let us know in the comments.
As Khalid proved—we are listening, and we ship the updates you ask for.