How commercetools/telefonistka works
Main Components
a) Core Components:
• GitHub Webhook Server
• Promotion Engine
• Version Bumping Service
• Webhook Multiplexer
• ArgoCD Integration Service
• Configuration Manager
b) External Systems:
• GitHub API (REST & GraphQL)
• ArgoCD API
• Target GitOps Repositories
• Prometheus (for metrics)
Component Relationships and Architecture
Top Layer: External Systems
Middle Layer: Core Telefonistka Services
Bottom Layer: Internal Libraries and Utilities
Specific Implementation Details
a) Incoming Webhooks Flow:
• GitHub webhook → Webhook Server → Event Processing
• Multiplexing capability to multiple endpoints
b) Promotion Flow:
• Configuration Manager reads policies
• Promotion Engine analyzes changes
• GitHub API client creates PRs
• ArgoCD Integration provides deployment status
c) Version Bumping Flow:
• CLI commands → Version Bumper → GitHub API
• Supported methods (overwrite, regex, YAML)
Important Architectural Patterns to Highlight
• Plugin-style architecture for different version bumping strategies
• Event-driven webhook handling
• Configuration-driven promotion rules
• Service-oriented design with clear separation of concerns
Technical Details
• Go-based implementation
• REST/GraphQL API interactions
• File system interactions for GitOps
• Prometheus metrics endpoints
• Template-based PR generation
Specific Implementation Notes
• cmd/telefonistka: Entry points and core commands
• internal/pkg/: Core implementation packages
• argocd/: ArgoCD integration
• configuration/: Config management
• githubapi/: GitHub API clients
• prometheus/: Metrics handling
Key Flows to Emphasize
• Webhook reception → Event processing → Promotion analysis → PR creation
• Version bump command → File modification → PR creation
• Drift detection → Analysis → PR comments
• ArgoCD status → Manifest comparison → PR updates