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

Offen
#2,628 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
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
rust

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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