IdeaSift

Infrastructure teams struggle to tear down IaC-managed resources safely

Infrastructure engineers hit friction when removing Terraform- or CDK-managed environments: a destroy can be blocked by protection settings, prompt for irrelevant variables, or try to delete resources they want to keep. Teams also describe awkward review-workflow steps and manual workarounds. The reports point to a shared teardown problem, though most signals are Terraform-specific.

For infrastructure engineers and platform teams managing cloud resources with IaC. Mentioned from Jan 2016 to Aug 2023 on GitHub.

16 different people described this problem in 8 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
5.0/10
Pain
6.6/10
Frequency
10.0/10
Willingness to pay
0.0/10
Momentum
5.0/10
Who pays
Businesses
Competition
Medium
Build difficulty
Medium

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. We had to abandon terraform destroy because of the lack of this feature. As mentioned it does a sometimes undesirable procedure of deleting inner resources before deleting container
    jimsnab on GitHub (hashicorp/terraform)Aug 2021Has a workaroundAsked for a tool
  2. Currently been doing this with different projects/directories. But it would be nice to keep the entire stack together as one piece
    chadgrant on GitHub (hashicorp/terraform)Jan 2016Asked for a toolHas a workaround
Build brief

See what to build and who will buy it

  • 2 product ideas with the smallest useful version and pricing
  • 5 places to find your first customers
  • 14 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks