Dependency Graph Visualizer

Interactive tool to analyze and visualize LynqForm dependencies. Paste your YAML to see the execution order and detect cycles.

Load Example:

LynqForm YAML

apiVersion: operator.lynq.sh/v1 kind: LynqForm metadata: name: simple-app spec: hubId: my-hub # 1. Secret (no dependencies) secrets: - id: app-secret nameTemplate: "{{ .uid }}-secret" spec: stringData: password: "{{ randAlphaNum 32 }}" # 2. Deployment (depends on secret) deployments: - id: app-deployment dependIds: ["app-secret"] nameTemplate: "{{ .uid }}-app" spec: replicas: 2 template: spec: containers: - name: app image: nginx:latest # 3. Service (depends on deployment) services: - id: app-service dependIds: ["app-deployment"] nameTemplate: "{{ .uid }}-svc" spec: ports: - port: 80

Dependency Graph

3 resources found

100%

✅ Valid Dependency Graph

Execution order: app-secret → app-deployment → app-service

Resources are applied in topological order. Resources at the same level can execute in parallel.

Resource Dependencies

Order

Resource ID

Type

Dependencies

1

app-secret

Secret

None

2

app-deployment

Deployment

app-secret

3

app-service

Service

app-deployment

How to Use

1. Load an Example: Click one of the preset buttons above to load a sample LynqForm
2. Edit YAML: Modify the YAML in the left editor, or paste your own LynqForm
3. Analyze: Click the "🔍 Analyze Dependencies" button to visualize the dependency graph
4. Explore:
   • View the execution order with numbered badges
   • Hover over nodes to highlight them in both graph and table
   • Check for dependency cycles (shown in red)
   • See which resources can execute in parallel

What it Shows

• Nodes: Each resource in your form (Deployment, Service, Secret, etc.)
• Arrows: Dependencies between resources (A → B means "A depends on B")
• Numbers: Execution order (1 = first, 2 = second, etc.)
• Parallel Execution: Resources with the same number can run in parallel
• Cycles: Invalid circular dependencies shown in red with error message

Example Scenarios

Simple App

Basic 3-tier structure: Secret → Deployment → Service

Multi-Tier Stack

Complex 6-level architecture with namespace, database, application, and ingress

Parallel Resources

Demonstrates resources that can be created simultaneously

Cycle Detection

Shows what happens when you have circular dependencies (invalid configuration)

Tips

• Resources at the same execution level can be applied in parallel
• Use dependIds to control the order of resource creation
• Avoid creating dependency cycles - they will cause reconciliation to fail
• Keep dependency chains shallow for better performance

Related Documentation

• Dependencies Guide - Complete guide on defining dependencies
• Templates Guide - Learn about LynqForm structure
• Policies Guide - Resource lifecycle policies

---

Need Help?

If you encounter issues with your form, check the Troubleshooting Guide or review the error message shown by the visualizer.