Add Core Hub staging deployment profile

This commit is contained in:
2026-06-27 21:11:46 +02:00
parent f280f9b0f8
commit b895d1f772
12 changed files with 519 additions and 2 deletions

View File

@@ -38,6 +38,11 @@ state_hub_task_id: "e0ea0928-a3ea-4ece-bbb7-ee08f8a3279b"
Import production-safe or full approved Inter-Hub data into Core Hub staging. The importer is ready; this now waits on an approved Inter-Hub export bundle and target staging database. Record counts and discrepancies from the generated migration report.
2026-06-27 continuation: `CORE-WP-0008-T04` added the Core Hub staging
deployment profile and migration job/runbook. This task still waits for an
approved Inter-Hub export bundle and provisioned staging database before an
actual import can run.
## Dual-Run Smokes
```task

View File

@@ -159,7 +159,7 @@ deployed execution gate rather than an implementation blocker.
```task
id: CORE-WP-0008-T04
status: todo
status: done
priority: high
state_hub_task_id: "fc53da17-485d-438c-986f-38d688d75b51"
```
@@ -178,6 +178,19 @@ Minimum scope:
Done when Core Hub can be deployed to staging and used by T02/T03 smokes without
one-off shell reconstruction.
Completed 2026-06-27: added the service-repo staging deployment profile:
Dockerfile, `.dockerignore`, `k8s/railiance-staging/` namespace/runtime
manifests, `docs/deployment/staging-profile.md`, `make
staging-profile-check`, `make container-build`, and test coverage for the
profile checker. The profile defines staging runtime config, database and
secret references, Alembic migration job, health/readiness probes,
Railiance-style build/apply commands, rollback notes, and the `CORE-WP-0005-T02`
staging import handoff. Verified with `make staging-profile-check`,
`make lint`, `make test`, and `make container-build
IMAGE_REPOSITORY=core-hub IMAGE_TAG=staging-profile-check`. It
intentionally does not contain plaintext secret values or claim that a real
staging cluster has already been deployed.
## Task: Add CLI wrappers after API proof
```task