trade-next/trade-gitops
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(sol): align canary ingestor and api auth
All checks were successful
deploy-trade-r001-canary / apply (push) Successful in 6m14s
Details

Browse Source
This commit is contained in:
mpabi
2026-04-12 18:30:30 +02:00
parent 59507521d6
commit 2e909026a7
5 changed files with 199 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
environments/sol/trade-r001-canary/README.md
View File

@@ -50,9 +50,10 @@ Minimal canary namespace for migration baseline `R001` on `sol`.
- The canary workflow re-runs:
- `postgres-migrate`
- `hasura-bootstrap`
- `api-token-seed`
before it waits for `Hasura`, `trade-api`, `trade-frontend`, `trade-ingestor`, and the DLOB hot/all-path deployments to become healthy.
- The current canary `trade-ingestor` is intentionally pinned to the schema already reconstructed on `sol` and reads from `dlob_stats_latest`.
- The exact live `R001` ingestor path that reads `dlob_*_derived_latest` remains a follow-up substep after the DLOB writer chain is reconstructed.
- The canary `trade-ingestor` now follows the live `R001` path on `sol`: it reads `dlob_hot_derived_latest` first for hot markets and falls back to `dlob_all_derived_latest`.
- `api-token-seed` restores the frontend read token in `api_tokens`, so `trade-api` and `trade-frontend` can be validated against the reconstructed derived tables after each deploy.
## Operator Flow