Trace: verify Pi control-plane attestation at push

Abierto
  • ¿Algo no está bien?
#3,718 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
security, testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

component/CLI component/controlplane trace-provider

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-trace blocks 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.

Lenguaje dominante
Go
Estrellas
582
Forks
61
Merge medio
12 h 47 min
PR fusionados (30 d)
137

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de chainloop-dev/chainloop

Todos los issues de chainloop-dev/chainloop

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.