Terraform Dependency Visualizer

How it works

Your pasted .tf source is scanned with regular expressions for resource, data, and module block headers, then each block's body is matched for references to other declared blocks — type.name attribute lookups, module.name references, and explicit depends_on entries — to build a dependency graph, which is then arranged into layers by a topological sort so the SVG reads top to bottom in apply order.

FAQ

Will this catch every dependency a real terraform plan would find?

No — it only detects dependencies visible as text references in your pasted source (type.name.attr, module.name.output, explicit depends_on); implicit dependencies that a provider computes during a real plan aren't visible from static text and won't be caught.

What happens if my configuration has a dependency cycle?

Nodes that can't be resolved into a clean order are dumped together into one final layer rather than causing an error — a genuine cycle would fail inside real Terraform anyway.