Use cases / Platform, SRE and on-call
Seeing which running systems a change reaches
The diff says rds.tf. The map says orders-db, the API in front of it, and the queue behind it.
The problem
Code review happens in files; incidents happen in systems. The reviewer rarely knows that a Terraform tweak removes deletion protection from the production database.
What visualdiff does
- Terraform resources, Kubernetes objects, env vars and hostnames are extracted from the change.
- They are matched against your ArchCanvas map, live from your cloud accounts.
- The report shows the matched resources and their neighbours one and two hops away, and opens the change on the live map.
In the sample, the change reaches orders-db and orders-api, with 24 resources nearby.
Related
- Reviewing pull requests written by agentsAgents open pull requests faster than anyone can read them. Read the 10% that decides whether it is safe.
- Large refactors that hide a behaviour changeA refactor is supposed to change nothing. Find the one line that does.
- Stopping hallucinated dependenciesSlopsquatting: attackers register the package names models invent. Catch them at review.
- Knowing whether review is keeping upThe sanity index: is the codebase getting harder to review as more of it is written by machines?