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

未关闭
#2,628 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
rust

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。