breg: operator HTTP reads and actions for import runs, blocked Proposal applications and hook dead letters

Aperta
#2,734 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
node.js, python, rust
Ambito
api, backend

Direzione di ricerca

Start by reading crates/registry-breg/src/api/ingestion.rs and crates/registry-breg/src/ingestion_store.rs to see how import runs are currently scoped to their creator, then find an existing product's operator routes to copy the list/detail shape from. Map the three read routes (import runs, blocked Proposal applications, dead-lettered hook deliveries) before touching the actions, since actions depend on the reads. Done means list and detail routes with state, age and cursor paging, action routes with reason and idempotency key, maintained Rust/Node/Python client methods, and disclosure-profile plus security notes in the pull request.

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

Descrizione

Operators can find stuck BReg work only through bregctl on the host, and some of it not at all.

Today

  • Import runs can be read only by their creator (crates/registry-breg/src/api/ingestion.rs, crates/registry-breg/src/ingestion_store.rs). No operator-wide list or detail exists.
  • Blocked Proposal applications are a gauge (breg_proposal_application_blocked_jobs), not a list.
  • Hook dead letters are visible only through the CLI, and the list can fail or omit rows (#1798, #1796).
  • There is no HTTP route for any hook, timer or retention action, and CLI actions carry no named person.

Ask

Read routes:

  • Import runs across creators, by state, with a detail read.
  • Blocked Proposal applications, with the failure class and age.
  • Outbound hook deliveries by state, including dead-lettered.

Actions, after the reads:

  • Retry or discard a dead-lettered hook delivery.
  • Requeue a blocked Proposal application.

Shape

These routes follow the same shape as the other products' operator routes. It is a convention, not a shared contract:

  • A list of held or failed work with state, age and cursor paging, plus a detail read.
  • Actions only after the reads ship. Each action takes one item at a time, with a reason and an idempotency key. The product's own access profile authorises it for a named person's token, and the audit records it under that person.
  • Maintained client methods (Rust, and the Node and Python facades) in the same change.
  • An operator disclosure profile. The routes return identifiers, states, ages and failure classes, not record content or personal data.
  • Security review notes in the pull request, because each route widens what an operator token can read or change.

Related: #1492 (import run management), #1432, #2096, #1798, #1796.

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.