BReg: a read route for the hook delivery state of a record

Aperta
#2,627 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
openapi, rust

Direzione di ricerca

Read the existing hook delivery and access profile behavior, then inspect the generated API contract and the profile model in explain; the issue does not name specific source or test files. Add a read route scoped to records and hook names the caller may access, returning only hook name, time, and delivery state. Done when the route is in the generated contract, profile behavior is covered in explain, and tests verify access refusal and dead-letter output excludes payload values and destinations.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:breg criticality:p3 enhancement studio:product-gap

Problem

After a record changes, BReg delivers hooks on a best-effort basis; a failed delivery ends as a dead letter. Only an operator sees it, through bregctl hook list. A service that sends a payment instruction after a change cannot tell the people working the record that the instruction never left, because there is no public route and no application surface for it.

Smallest change

  • A read route that returns, for one record the caller may read, the delivery state of the hooks it caused: pending, delivered, or dead-lettered, with the hook name and time, and nothing from the payload.
  • Scoped by the caller's access profile: a profile sees the state only for records and hook names it is granted.
  • A follow-up in App Kit can show a banner from it; that is a separate change in the kit repository.

Acceptance

  • A profile granted the record can read its hook delivery state, and a profile not granted it is refused with the usual problem.
  • A test shows a dead letter surfacing as dead-lettered with no payload value and no destination in the answer.
  • The route appears in the generated API contract and is covered by the profile model in explain.

Out of scope

  • Replay or discard from the route (operators keep bregctl hook).
  • Delivery state for other products' outboxes.
  • The App Kit banner.

Related

  • #2129, #2204
Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.