evidence: read-only operator route for activated authority, source health and signer state
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- api, backend, observability
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
/readyignores 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.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 151
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:breg enhancement
难度 2/5 1-3 小时 新手友好度 65/100
registrystack/registry-stack#2765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
registrystack/registry-stack#2761 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
registrystack/registry-stack#2743 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2706 ·
维护者通常 1 天内回复
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory未关闭
难度 2/5 1-3 小时 新手友好度 83/100
registrystack/registry-stack#2704 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100