Skip to main content

​
Find the code behind a running resource

Ask Annie which Terraform module manages a running resource. Anyshift connects your live infrastructure, Terraform state, and code so you can trace the resource back to its declaration and identify differences. Terraform code instantiates Terraform state, which manages live infrastructure Declared resources are linked to the state that instantiated them, and state entries are linked to the live resources they manage. That’s how Annie answers questions that span layers: “Which module deployed this pod?”, “What code manages this RDS instance?”, “Which resources are running without any Terraform backing?”
The same model applies to Kubernetes: declared manifests (or Helm charts) → live cluster state, streamed by the Anyshift agent.

​
See the graph

Annie can also draw the graph. Ask “map our cluster” or “diagram the dependencies of the payment service” and she renders the live topology from the knowledge graph as a diagram you can read at a glance.
Annie-generated Mermaid diagram of a Kubernetes production cluster topology

A live Kubernetes topology Annie drew from the knowledge graph: ingress, namespaces, workloads, and the cross-layer dependencies between them.

The diagram comes from the same graph that powers Explore & Ask, so it shows what is actually running right now: real resource names, live dependencies, and gaps like a missing config or an unmanaged instance. No stale wiki sketch.

​
Working with diagrams

Explore

Zoom, pan, and open any diagram fullscreen to follow a dependency chain across layers.

Saved to your library

Every diagram lands in Artifacts → Diagrams, so you can reopen and share it later.

Standard Mermaid

Diagrams are plain Mermaid. Copy the source and paste it into GitHub, Notion, or any Mermaid-compatible tool.

From any surface

Ask for a diagram in a conversation, and dig deeper with a follow-up question right where you are.

​
What You Can Ask Annie

  • “Which Terraform module created this EC2 instance?”
  • “Show me all resources defined in the networking module”
  • “What variables does this state file use?”
  • “What resources were modified outside of Terraform this week?”
  • “Which live resources have no Terraform backing?”
  • “Are my declared replicas matching the pods actually running?”
See the Drift Detection page for more.
  • “What breaks if I destroy this module?”
  • “Which services depend on this security group?”
  • “If I change this variable, what resources are affected?”

​
Connect sources and check drift

Terraform

How Annie ingests Terraform code and state, and what she does with them.

Kubernetes (Live)

How Annie streams live cluster state and ties it to your declared K8s manifests.

Drift Detection

Find the gap between what you declared and what’s actually running.

Production Graph

How all of this connects under the hood.