Integrations
Central catalog and connector hub for managing external tool integrations across the Stella Ops platform.
Purpose
Integrations provides a unified API for registering, configuring, and health-checking third-party service connectors such as GitHub, GitLab, and Harbor. It serves as the single source of truth for all external tool configurations, enabling other modules to discover and consume integration details without embedding provider-specific logic.
Quick Links
- Architecture - Technical design and implementation details
Status
| Attribute | Value |
|---|---|
| Maturity | Production |
| Source | src/Integrations/ |
Key Features
- Plugin-based connector architecture: Extensible provider system with built-in connectors for GitHub App, GitLab, Harbor, and in-memory testing
- Health checks: Per-integration health probing with status tracking and alerting
- Credential management: AuthRef URI scheme for vault-referenced credentials; no plaintext secrets stored in the integration catalog
- Tenant isolation: All integrations are scoped to a tenant; cross-tenant access is prohibited
- AiCodeGuard pipeline support: Integrations participate in AI-assisted code review pipelines
- Plugin discovery: Automatic detection and registration of available connector plugins
Dependencies
Upstream (this module depends on)
- Authority - Authentication and authorization for API access
- Plugin Framework - Plugin lifecycle and discovery infrastructure
Downstream (modules that depend on this)
- Scanner - Retrieves repository and registry connection details for scanning operations
- Orchestrator - Reads integration configs for CI/CD pipeline orchestration
- Signals - Uses integration metadata for SCM webhook routing and validation
Configuration
Key settings:
- PostgreSQL connection (database:
stellaops_integrations) - Authority audiences and scopes
- Plugin search paths for connector discovery
- Health check intervals and timeout thresholds
IDE Extensions (VS Code, JetBrains)
As of Sprint 214, the IDE extension plugins (previously src/Extensions/) are housed under src/Integrations/__Extensions/. These are non-.NET projects (TypeScript for VS Code, Kotlin for JetBrains) that act as thin API clients for the Orchestrator and Authority services. See the Architecture doc for details.
Related Documentation
- Plugin Framework - Underlying plugin infrastructure
- Scanner - Primary consumer of integration configs
- Orchestrator - Pipeline orchestration using integrations
- Signals - SCM webhook processing