Trace: verify Pi control-plane attestation at push
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- go
- 領域
- security, testing-qa
研究方向
Start by reading the Pi support baseline in #3704 and the existing attestation-at-push matrix and smoke-test entry points. Set up the authorized disposable control-plane workflow with pinned Pi, CLI, and model versions, then trace one commit through upload and signature verification. Done means the signed attestation matches the Pi run, rejected credentials cause no upload, push failure behavior matches both modes, and only this matrix cell is updated after live assertions pass.
由索引模型根據 Issue 內容生成。
描述
Problem
Pi's attestation-at-push matrix cell is Unknown because the default local E2E suite writes unsigned local evidence and does not exercise a control-plane upload.
Scope
Add an opt-in, isolated Pi control-plane smoke that verifies a signed session attestation for a traced push. This issue covers only upload and cryptographic attestation; the other Pi notification cells are tracked separately.
Acceptance criteria
- Provision an authorized disposable control-plane workflow; pin Pi, CLI, and model versions without using the local-only matrix runner.
- Make one Pi-traced commit and push it; retrieve and cryptographically verify the signed attestation.
- Match session ID, commit SHA, transcript, model, token usage, and attribution to the Pi run.
- Rejected credentials produce no upload.
--require-traceblocks a failed push while default mode remains fail-open. - Use event/state synchronization instead of fixed sleeps. Update only the attestation-at-push Pi matrix cell after the live assertions pass.
Non-goals
- Pi welcome notification (#3722).
- Credentials warning in Pi UI (#3723).
- Session URL after push (#3724), which depends on a successful upload here.
- Granting permission to a production Chainloop project or bypassing Pi project trust.
Baseline Pi support #3704. The original combined verification issue was narrowed to this one cell as part of the issue-first tracking pass.
- 主要語言
- Go
- 星號
- 582
- 分支
- 61
- 平均合併
- 12 小時 47 分鐘
- 30 天內合併 PR
- 137
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
chainloop-dev/chainloop 的其他 Issue
-
feature-parity trace-provider
難度 2/5 1-3 小時 新手友好度 70/100
chainloop-dev/chainloop#3802 ·
維護者通常 1 天內回覆
-
bug trace-provider
難度 4/5 3-5 天 新手友好度 48/100
chainloop-dev/chainloop#3803 ·
維護者通常 1 天內回覆
-
feat(trace): support GitHub Copilot (CLI and VS Code) in Chainloop Trace可能已有人在做 @migmartri 今天認領。 未關閉Feature spec trace-provider
chainloop-dev/chainloop#3800 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Allow enabling policy enforcement at the workflow contract level可能已有人在做 @migmartri 於 10 天前認領。 未關閉component/backend new-policy spec
chainloop-dev/chainloop#3762 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
chainloop component/CLI performance trace-provider
難度 4/5 3-5 天 新手友好度 62/100
chainloop-dev/chainloop#3756 ·
維護者通常 1 天內回覆
查看 chainloop-dev/chainloop 的全部 Issue
相似的 Issue
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
維護者通常 1 天內回覆
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
model:sonnet runtime:claude security size:S
難度 2/5 1-3 小時 新手友好度 78/100
FootprintAI/Containarium#3624 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆