Evidence: serve more than one public-check definition in one process

Abierto
#2,628 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
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Start by locating the public-check request handler, its definition configuration, and the evidencectl check validation entry point; the issue does not name specific files or tests. Trace how one definition is loaded and how requests produce the current non-revealing answer, then identify how multiple definitions can be selected without path collisions. Done means two definitions work in one process, collisions are rejected, both wrong-code cases stay non-revealing, and the published example runs with two definitions.

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

Descripción

area:evidence criticality:p2 enhancement studio:product-gap

A printed certificate can carry a QR code that opens a page showing whether the certificate is valid, suspended, revoked or expired. POST /v1/public-check answers that, but one Evidence process serves one definition. A deployment with two certificate types (for example a licence and a statement of good standing) has to run and operate a second Evidence process for the second one.

Smallest change

  • Several public-check definitions in one process, each at its own path or selected by a field of the request.
  • evidencectl check validates each definition and refuses two that would answer at the same path.

Acceptance

  • One Evidence process serves two public-check definitions, and a wrong number or code for either gives the same non-revealing answer as today.
  • evidencectl check refuses two definitions that collide.
  • The published public-check example runs with two definitions.

Out of scope

  • Promoting the contract from v1alpha1 and signing the answer; both are separate decisions.
  • Generating the check code and its registry field (the issuing app and authoring tools do that).
  • Rate limit or abuse policy changes beyond what exists.
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.