evidence: read-only operator route for activated authority, source health and signer state

Aperta
#2,739 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
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
nodejs, python, rust

Direzione di ricerca

Start by finding the existing /ready handler and the operator routes the other products expose, since this issue says they are the convention to copy rather than a shared contract. Read how activated authority, activation history, source health and signer state are currently obtained from the CLI or files, then sketch the read-only list and detail shapes over those sources. The same change must add client methods to the Rust crate and the Node and Python facades, plus an operator disclosure profile, so expect several files; done means the routes return identifiers, states, ages and failure classes only, with security notes in the pull request.

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

Descrizione

An Evidence operator cannot read the activated authority or the health of sources over HTTP.

Today

  • Activated authority, activation history, source health and signer state are CLI or file only.
  • /ready ignores sources and stale extracts.
  • Activation stays a CLI action that takes effect on restart. This issue does not change that.

Ask

A read-only operator route, with no actions:

  • The activated authority and its activation history, as identifiers and digests.
  • Per-source health: last success, last failure class, extract age.
  • Signer state: key identifier and certificate expiry.

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.
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.