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

Aberta
#2,628 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
58/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Rust
Estrelas
2
Forks
0
Merge médio
9h 48min
PRs com merge (30d)
151

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de registrystack/registry-stack

Todas as issues de registrystack/registry-stack

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.