Infrastructure Sync (Living Diagrams)
Infrastructure Sync converts real infrastructure files into OpenFlow diagrams deterministically. It works offline for supported inputs and produces diagrams that stay close to your actual infrastructure sources.
Supported formats
Section titled “Supported formats”- Terraform State (
.tfstateJSON) - Kubernetes YAML
- Docker Compose YAML
- Terraform HCL through the AI-assisted path when needed
When to use it
Section titled “When to use it”Use Infrastructure Sync when:
- you already have real infrastructure files
- you want deterministic parsing
- you need an offline-friendly import path
- you want an editable starting point for architecture review
Why it is different from AI import
Section titled “Why it is different from AI import”AI import is useful when the model needs to interpret messy or conceptual input. Infrastructure Sync is for cases where the source artifact already contains the structure and you want OpenFlowKit to parse it rather than reinterpret it.
That distinction matters for trust. If the goal is to stay close to the underlying infra source, deterministic parsing is usually the better first move.
How to use it
Section titled “How to use it”- Open Studio.
- Switch to the Infra tab.
- Select the matching format (Terraform State, Kubernetes YAML, or Docker Compose).
- Paste or drop the file contents into the text area.
- Click “Generate” to create the diagram.
- Review the summary showing nodes and connections found.
- Click “Apply” to add the diagram to the canvas.
Supported File Types
Section titled “Supported File Types”- Terraform State (
.tfstate): Parses resources and their relationships from Terraform state output - Kubernetes YAML: Parses deployments, services, pods, and their connections
- Docker Compose YAML: Parses services, networks, and volumes
After import
Section titled “After import”The result is still an editable OpenFlowKit diagram. After applying it to the canvas, you can:
- annotate it
- regroup it
- run layout
- export it
- compare it against later snapshots
- apply lint rules for architecture review
Best use cases
Section titled “Best use cases”- cloud topology reviews
- current-state architecture documentation
- infra change communication
- turning operational source files into something easier to discuss visually