How terramate-io/terramate works
Main Components
a) Core Engine Components:
• HCL Processing (/hcl directory)
• Stack Management (/stack directory)
• Code Generation (/generate directory)
• Run Orchestration (/run directory)
• Cloud Integration (/cloud directory)
b) CLI Interface:
• Command Processing (/cmd/terramate/cli)
• Output Handling (/cmd/terramate/cli/out)
• Configuration Management (/cmd/terramate/cli/cliconfig)
c) VCS Integration:
• GitHub Integration (/cmd/terramate/cli/github)
• GitLab Integration (/cmd/terramate/cli/gitlab)
• BitBucket Integration (/cmd/terramate/cli/bitbucket)
Interaction Flows
Following key interactions:
a) Primary Flow:
User Input -> CLI Interface -> Stack Manager -> Orchestration Engine -> Infrastructure Providers
b) Code Generation Flow:
Stack Configuration -> Generator -> HCL/JSON/YAML Output -> Infrastructure Code
Component Details
Specific elements:
a) Core Engine:
• Terramate Core |
• Stack Management |
• Code Generation |
• Change Detection |
• Orchestration |
b) Integration Layer:
• Integration Layer |
• Terraform |
• OpenTofu |
• Terragrunt |
• VCS Systems |
Key Relationships
Critical relationships:
• Stack Dependencies (using DAG representation)
• Code Generation Flow
• Change Detection Paths
• Cloud Integration Points
Additional Elements
Include:
• Version control integration points
• Cloud service connection points
• State management flow