messaging: operator queue and attempt reads over HTTP, and retry and settle under a named person

Offen
#2,736 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
node.js, python, rust
Bereich
api, backend, security

Rechercherichtung

Start in crates/registry-messaging/src/http.rs to see how the existing get, cancel and receipt routes are wired, then read crates/registry-messaging/src/dispatch.rs for the queue, attempt and audit code that currently uses the fixed operator-tool actor. The issue sets the shape but not the endpoint names, paging fields or access profile, so confirm those against the convention used by the other products' operator routes before writing anything. Done means read routes for queue-by-state-and-age and per-message attempts, the retry and settle actions audited under the named person, matching Rust/Node/Python client methods, and security review notes in the pull request.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Messaging offers get and cancel for one message over HTTP. Everything else an operator does to the queue is a messagingctl command on the host.

Today

  • HTTP routes: submit, get one message, cancel, receipt, preview, provider callback (crates/registry-messaging/src/http.rs).
  • Listing the queue, retrying and settling are CLI only. Their audit records carry the fixed actor operator-tool (crates/registry-messaging/src/dispatch.rs), not a named person.
  • No metric gives the age of the oldest queued message.

Ask

Read routes:

  • The dispatch queue by state and age.
  • The attempt history of one message.

Actions, after the reads:

  • Retry and settle over HTTP, audited under the named person.

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.
Vorherrschende Sprache
Rust
Sterne
2
Forks
0
Ø Merge
9 Std. 48 Min.
Gemergte PRs (30 T.)
151

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus registrystack/registry-stack

Alle Issues in registrystack/registry-stack

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.