evidence: read-only operator route for activated authority, source health and signer state

オープン
#2,739 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
nodejs, python, rust

調査の方向性

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.
  • /ready ignores 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分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。