How otto-de/gitactionboard works
Main Components Identification
The system consists of two primary components:
• Frontend (Vue.js application)
• Backend (Spring Boot Java application)
Client Layer
• Vue.js Frontend Application
• Components for different dashboards (Workflow, CodeStandardViolations, Secrets)
• Authentication UI (Login Page)
Backend Services
• REST API Controllers
• Domain Services
• Adapters Layer
• Security Layer
External Systems
• GitHub API
• Microsoft Teams (for notifications)
Caching Layer
• In-memory cache for GitHub API responses
b. Component Relationships:
[Frontend Components] ←→ [Backend REST Controllers]
[Backend Controllers] ←→ [Domain Services]
[Domain Services] ←→ [Adapters]
[Adapters] ←→ [External Systems (GitHub/MS Teams)]
Specific Implementation Details
a. Frontend (Blue):
• Main Dashboard Component
• Authentication Components
• Monitoring Components (Workflows/Secrets/Code Standards)
b. Backend (Green):
• Controllers Package
• GithubController
• GithubAlertsController
• ConfigurationController
• BasicAuthenticationController
c. Services (Yellow):
• WorkflowService
• CodeStandardViolationsService
• SecretsScanService
• NotificationsService
d. External Systems (Gray):
• GitHub API
• MS Teams Webhook
Following flows:
• User requests → Frontend → Backend
• Backend → GitHub API (with caching)
• Backend → MS Teams (for alerts)
• GitHub API responses → Cache → Backend → Frontend
Additional Elements
Annotations for:
• Authentication mechanisms (Basic Auth & GitHub OAuth2)
• Caching configuration
• API rate limiting
• Security boundaries
Technical Details to Highlight
• Spring Boot backend architecture
• Vue.js frontend structure
• RESTful API endpoints
• Authentication flows
• Caching mechanism
• Monitoring capabilities