coulomb/core-hub
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add deployed API smoke harness

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 20:17:08 +02:00
parent 451c82f1b7
commit 2cddf8c94c
6 changed files with 788 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/specs/testing-release-and-migration.md
View File

@@ -25,6 +25,30 @@ Install the Chromium runtime once per workstation with:
make playwright-install
```
## Deployed API Smoke
The deployed `/api/v2` smoke harness is run with `make deployed-smoke`. It
expects `CORE_HUB_BASE_URL` plus an approved operator token supplied through
`CORE_HUB_OPERATOR_TOKEN_FILE` or the environment variable named by
`CORE_HUB_OPERATOR_TOKEN_ENV` (default: `CORE_HUB_OPERATOR_TOKEN`). The harness
never prints token values.
Example staging invocation:
```bash
CORE_HUB_BASE_URL=https://core-hub-staging.example.invalid \
CORE_HUB_OPERATOR_TOKEN_FILE=/secure/operator/path/core-hub-operator-token \
CORE_HUB_SMOKE_OUTPUT=.local/smoke/core-hub-staging.json \
make deployed-smoke
```
The JSON report contains health/readiness status, catalog and protected-route
checks, created smoke ids, counts, event ids, and API key prefixes only. If the
harness creates a runtime key for the smoke API consumer, set
`CORE_HUB_RUNTIME_TOKEN_OUTPUT` to an operator-controlled 0600 path and move the
value into the approved custody system immediately. Do not commit `.local/`
reports or runtime token files.
## Release Gates
A Core Hub release cannot replace Inter-Hub until: