feat: public report status derived from the cluster #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/status"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Server half of BUG-9 (the client half is in the bread repo, breadbug PR). Stacked on #6.
GET /v1/reports/{receipt}/statusnow reflects triage instead of always sayingreceived:receivedduplicateinvestigatingfixed(+fixed_in)closedMerged clusters report their target's state. The endpoint is rate limited per network bucket, receipts are 128-bit random, and nothing about the cluster or other reporters is revealed.
Tests: the full progression received -> duplicate -> investigating -> fixed -> closed, merged cluster follows its target, quarantined looks received, unknown receipt 404, rate limit.
Closes BUG-9
GET /v1/reports/{receipt}/status now reflects triage: received, duplicate (a known problem), investigating, fixed (with the fix version when one was recorded) or closed. Merged clusters report their target's state; quarantined reports look merely received; the endpoint is rate limited and reveals nothing else about the cluster or other reporters. Refs BUG-916412d07f1c6a7996196