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

Ouverte
#2,736 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
node.js, python, rust
Domaine
api, backend, security

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.