Krow/Krow-workspace
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(notifications): replace Cloud Run job with worker service

Browse Source
This commit is contained in:
zouantchaw
2026-03-16 17:54:25 +01:00
parent 73287f42bd
commit 515a6f2bed
6 changed files with 206 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/BACKEND/API_GUIDES/V2/README.md
View File

@@ -107,7 +107,7 @@ Important operational rules:
- background location streams are stored as raw batch payloads in the private v2 bucket and summarized in SQL for query speed
- incident review lives on `GET /client/coverage/incidents`
- confirmed late-worker recovery is exposed on `POST /client/coverage/late-workers/:assignmentId/cancel`
- queued alerts are written to `notification_outbox`, dispatched by Cloud Run job `krow-notification-dispatcher-v2`, and recorded in `notification_deliveries`
- queued alerts are written to `notification_outbox`, dispatched by the private Cloud Run worker service `krow-notification-worker-v2`, and recorded in `notification_deliveries`
## 5) Route model

3
docs/BACKEND/API_GUIDES/V2/unified-api.md
View File

@@ -185,7 +185,8 @@ These are exposed as direct unified aliases even though they are backed by `core
- SQL token registry in `device_push_tokens`
- durable queue in `notification_outbox`
- per-attempt delivery records in `notification_deliveries`
- Cloud Run job `krow-notification-dispatcher-v2`
- private Cloud Run worker service `krow-notification-worker-v2`
- Cloud Scheduler job `krow-notification-dispatch-v2`
### Push token request example