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

Abierto
#2,739 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nodejs, python, rust

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.