Terraform shows what changes. Not what it breaks.
A plan lists the resources you changed. It won't tell you what depends on them. To find that out you read depends_on by hand, run terraform graph, pipe the output through graphviz, and squint at an SVG — manual inspection, every time, and only within a single state.
One command. Every dependent, ranked.
Point stategraph blast-radius at a resource and it traverses the graph for you — distance 0 is the change, distance 1 is everything directly affected.
❯ stategraph blast-radius "module.scrum.data.google_compute_network.shared_network_dev" DISTANCE RESOURCE 0 module.scrum.data.google_compute_network.shared_network_dev ← the change 1 module.scrum.google_redis_instance.agent_sandbox 1 module.scrum.google_redis_instance.memorystore_jobs 1 module.scrum.google_memcache_instance.memorystore 1 module.scrum.google_redis_instance.memorystore_v2
distance 0 = the changed resource · distance 1 = directly affected dependents
From guesswork to risk you can see
depends_on by handterraform graphWhat you get
Distance metric
Every dependent comes with a number: 1 is directly affected, 2+ is indirectly downstream. Read risk at a glance instead of tracing edges.
Pre-apply risk assessment
See the full set of resources a change touches before you run apply — not after something downstream falls over in prod.
Interactive graph explorer
Prefer to click around? Explore the same dependency graph visually in the dependency graph explorer.
Spans state boundaries
Dependents in other states show up too. Blast radius doesn't stop at the edge of a single state file.
Find hub resources
A resource with a large blast radius is a hub — the things you change most carefully. Now they're easy to spot.
Built in, not bolted on
No graphviz, no extra plugin. Blast radius is part of the graph Stategraph already keeps.
See your blast radius
Stop rendering SVGs to guess what a change touches. Point Stategraph at a resource and get every dependent, ranked by distance, across your whole graph.