mirror of
https://github.com/azaion/annotations.git
synced 2026-06-21 12:51:06 +00:00
03f879206e
This commit captures everything produced during autodev existing-code Steps 1 (Document), 2 (Architecture Baseline Scan), and 3 (Test Spec), together with the targeted auth + CORS re-sync triggered on 2026-05-14 when codebase drift was detected at Step 4 entry. None of this work was previously committed. Step 1 (Document) — 50+ _docs/02_document/ files: problem, solution, architecture, system flows, glossary, module-layout, per-component specs (01..06), modules, deployment, diagrams, data model, FINAL report, verification log, discovery. Step 2 (Architecture Baseline) — architecture_compliance_baseline.md. Verdict PASS_WITH_WARNINGS (0 Critical, 0 High, 1 Medium, 2 Low). No High/Critical findings; auto-chained to Step 3 per existing-code flow. Step 3 (Test Spec) — _docs/02_document/tests/* (67 scenarios across blackbox, security, resilience, resource-limit, performance), plus e2e/docker-compose.test.yml, e2e/seed/run.sh, scripts/run-tests.sh, scripts/run-performance-tests.sh. Coverage 88% over the active scope (40 of 45 items covered, 6 RB-deferred, 5 documented-as-uncovered). Targeted auth + CORS re-sync — replaces the deleted in-house token issuer with a JWKS-verifier model. AuthController and TokenService removed; JwtExtensions switched from HS256 symmetric to ES256 over admin's JWKS. ConfigurationResolver and CorsConfigurationValidator added under src/Infrastructure/. ADR-002 and ADR-006 retired; SEC-01, SEC-02, SEC-03 marked Closed. One new testability risk recorded in architecture.md Open Risks Section 6 (JWKS HTTPS gating). Source changes: - src/Auth/JwtExtensions.cs (modified) — ES256, JWKS, alg pinning - src/Program.cs (modified) — DI wiring for ConfigurationResolver and CorsConfigurationValidator - src/Controllers/AuthController.cs (deleted) — no in-service issuance - src/Services/TokenService.cs (deleted) — same - src/Infrastructure/ConfigurationResolver.cs (new) - src/Infrastructure/CorsConfigurationValidator.cs (new) - .env.example (new) — required env var documentation - .gitignore (updated) Cross-repo coordination: _docs/cross-repo/flights_h1_h2_h3_change_spec captures the change-spec for downstream services that consumed the now deleted /auth endpoints. Co-authored-by: Cursor <cursoragent@cursor.com>
2.2 KiB
2.2 KiB
Containerization
Source of truth: src/Dockerfile.
Build
Two-stage build:
- build stage —
mcr.microsoft.com/dotnet/sdk:10.0,--platform=$BUILDPLATFORM. Reads$TARGETARCHand runsdotnet publish -c Release -o /app --os linux --arch $arch(mappingamd64 → x64, otherwise$TARGETARCH). - runtime stage —
mcr.microsoft.com/dotnet/aspnet:10.0. Copies the published output, exposes port8080, setsENTRYPOINT ["dotnet", "Azaion.Annotations.dll"].
Build arguments
| Arg | Default | Purpose |
|---|---|---|
BUILDPLATFORM |
provided by Buildx | Multi-arch host platform |
TARGETARCH |
provided by Buildx | Output arch (amd64 / arm64) |
CI_COMMIT_SHA |
unknown |
Stamped into AZAION_REVISION env at runtime |
Runtime
| Aspect | Value |
|---|---|
| Base image | mcr.microsoft.com/dotnet/aspnet:10.0 |
| Working dir | /app |
| Exposed port | 8080 (HTTP) |
| Entry point | dotnet Azaion.Annotations.dll |
| Runtime env stamped at build | AZAION_REVISION = $CI_COMMIT_SHA |
Multi-arch
Dockerfile is multi-arch capable via Buildx. The current Woodpecker pipeline emits arm64 only (label platform: arm64, tag ${BRANCH}-arm). Producing amd64 requires an additional pipeline (or extending the existing one to a matrix).
Image size & caching
- Layers: SDK install →
COPY . .→ publish → runtime copy. The final layer is the published/appdirectory only — no SDK in runtime image. - Cache hit on
COPY . .is wide (entiresrc/); finer caching (e.g.,COPY *.csprojfirst, thendotnet restore, then sources) is not configured — improvement candidate.
Image labels
Set in CI (.woodpecker/build-arm.yml), not in the Dockerfile:
org.opencontainers.image.revision = $CI_COMMIT_SHAorg.opencontainers.image.created = $BUILD_DATEorg.opencontainers.image.source = $CI_REPO_URL
These follow the OCI standard so the registry surfaces them correctly.
Open items
- Add
amd64build target if non-ARM hosts are required. - Consider non-root user inside the runtime image (none configured today).
- Consider
dotnet restorecache layer split for faster CI builds.