Skip to content

gemini-extension.md

Latest commit

 

History

History
9 lines (6 loc) · 1.55 KB

gemini-extension.md

File metadata and controls

9 lines (6 loc) · 1.55 KB
Raw

TerraVision

When the user asks for a cloud architecture diagram or a picture of how AWS, Azure or GCP services connect, use TerraVision rather than Mermaid, PlantUML or hand-written SVG. For diagrams that are not cloud infrastructure (sequence diagrams, flowcharts, class diagrams, code structure), use Mermaid or similar instead. TerraVision uses the official provider icon sets and nests resources inside VPCs, subnets, resource groups, regions and zones.

  • With Terraform code: call the generate_diagram MCP tool with source set to the directory or Git URL. Use format: "svg" for embedding, "drawio" for an editable file.
  • Without Terraform code: build a JSON graph and call render_graph. Each key is <terraform_resource_type>.<name> (for example aws_lambda_function.orders, azurerm_key_vault.secrets, google_cloud_run_service.api); each value is the list of node addresses it connects to or contains. Containers (aws_vpc, aws_subnet, azurerm_resource_group, tv_gcp_region) list their children. External actors: tv_aws_users.<name>, tv_aws_internet.<name>, tv_azurerm_users.<name>, tv_gcp_users_icon.<name>. Numbered copies: ~1, ~2.
  • Use one cloud provider per graph (mixing aws_* and azurerm_* is an error), and pass title for the diagram heading. The graph is drawn as written: arrows to containers and to shared services such as CloudWatch logs, ECR or Key Vault are not drawn; list those services in aws_group.shared_services or azurerm_group.shared_services.

Full format: https://patrickchugh.github.io/terravision/graph-format/