Widen scratch iteration 011 with fixture-backed integrations QA
This commit is contained in:
@@ -8,6 +8,7 @@ Consolidated Docker Compose configuration for the StellaOps platform. All profil
|
||||
|--------------|---------|
|
||||
| Run the full platform | `docker compose -f docker-compose.stella-ops.yml up -d` |
|
||||
| Add observability | `docker compose -f docker-compose.stella-ops.yml -f docker-compose.telemetry.yml up -d` |
|
||||
| Start QA integration fixtures | `docker compose -f docker-compose.integration-fixtures.yml up -d` |
|
||||
| Run CI/testing infrastructure | `docker compose -f docker-compose.testing.yml --profile ci up -d` |
|
||||
| Deploy with China compliance | See [China Compliance](#china-compliance-sm2sm3sm4) |
|
||||
| Deploy with Russia compliance | See [Russia Compliance](#russia-compliance-gost) |
|
||||
@@ -22,6 +23,7 @@ Consolidated Docker Compose configuration for the StellaOps platform. All profil
|
||||
| File | Purpose |
|
||||
|------|---------|
|
||||
| `docker-compose.stella-ops.yml` | **Main stack**: PostgreSQL 18.1, Valkey 9.0.1, RustFS, Rekor v2, all StellaOps services |
|
||||
| `docker-compose.integration-fixtures.yml` | **QA success fixtures**: Harbor and GitHub App API fixtures for retained onboarding verification |
|
||||
| `docker-compose.telemetry.yml` | **Observability**: OpenTelemetry collector, Prometheus, Tempo, Loki |
|
||||
| `docker-compose.testing.yml` | **CI/Testing**: Test databases, mock services, Gitea for integration tests |
|
||||
| `docker-compose.dev.yml` | **Minimal dev infrastructure**: PostgreSQL, Valkey, RustFS only |
|
||||
@@ -203,6 +205,33 @@ docker compose -f docker-compose.testing.yml --profile all up -d
|
||||
|
||||
---
|
||||
|
||||
### QA Integration Success Fixtures
|
||||
|
||||
Use the fixture compose lane when you need a scratch stack to prove successful Integrations Hub onboarding for the providers currently exposed in the local UI (`Harbor`, `GitHub App`).
|
||||
|
||||
```bash
|
||||
# Start the fixture services after the main stack is up
|
||||
docker compose -f docker-compose.integration-fixtures.yml up -d
|
||||
|
||||
# Harbor success-path endpoint
|
||||
curl http://harbor-fixture.stella-ops.local/api/v2.0/health
|
||||
|
||||
# GitHub App success-path endpoints
|
||||
curl http://github-app-fixture.stella-ops.local/api/v3/app
|
||||
curl http://github-app-fixture.stella-ops.local/api/v3/rate_limit
|
||||
```
|
||||
|
||||
Fixture endpoints:
|
||||
|
||||
| Service | Hostname | Port | Contract |
|
||||
|---------|----------|------|----------|
|
||||
| Harbor fixture | `harbor-fixture.stella-ops.local` | 80 | `GET /api/v2.0/health` -> healthy JSON + `X-Harbor-Version` |
|
||||
| GitHub App fixture | `github-app-fixture.stella-ops.local` | 80 | `GET /api/v3/app`, `GET /api/v3/rate_limit` |
|
||||
|
||||
These fixtures are deterministic QA aids only; they are not production dependencies and remain opt-in.
|
||||
|
||||
---
|
||||
|
||||
## Regional Compliance Deployments
|
||||
|
||||
### China Compliance (SM2/SM3/SM4)
|
||||
|
||||
Reference in New Issue
Block a user