How camptocamp/terraboard works
Main Components Overview
The system architecture should be divided into these primary components:
a) Frontend Layer:
• Vue.js based web interface (located in /static/terraboard-vuejs)
• Components for state visualization, comparison, and search
• Client-side routing and state management
b) Backend Layer:
• Go server (main application)
• REST API endpoints
• State management and processing logic
• Provider integrations
c) Storage Layer:
• PostgreSQL database for internal state storage
• Multiple provider support for state files:
• AWS S3 + DynamoDB
• Google Cloud Storage
• Terraform Cloud
• GitLab
• S3-compatible providers (MinIO)
Key Interactions to Highlight
• Frontend → Backend API calls
• Backend → Various cloud providers for state retrieval
• Backend → PostgreSQL for state storage and querying
• Background sync process between providers and database
Detailed Component Breakdown
• State List View
• State Details View
• Search Interface
• Compare View
• Charts/Visualization
• API Server
• State Processor
• Provider Clients
• Database Sync Service
• AWS S3/DynamoDB
• Google Cloud Storage
• Terraform Cloud
• GitLab
• MinIO
Important Architectural Details
Specific elements:
• Authentication proxy support
• Base URL configuration
• Database synchronization interval
• Provider-specific configuration options
• State versioning support
• Lock management
Technical Specifications
• Technologies used (Go, Vue.js, PostgreSQL)
• Protocol information (HTTP/HTTPS)
• Authentication methods
• File formats (.tfstate)
Deployment Context
Deployment options:
• Docker container configuration
• Kubernetes deployment
• Database connection details
• Network boundaries
The security boundary with the authentication proxy
Use standardized symbols:
• Rectangles for services
• Clouds for external services
• Padlock symbols for security boundaries
• How data flows through the system
• Where state data is stored and processed
• How different providers are integrated
• Where to add new features or modifications
• Security boundaries and authentication flow