POL-3: cosign signing conditional — a fresh platform ships apps first-try #6
No reviewers
Labels
No labels
agent-work
agent-working
ultracode
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/app-template!6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/pol-3-cosign-conditional"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The POL-3
cosign signstep in release.yml + preview.yml was mandatory, but a freshly germinated platform seals only REGISTRY_TOKEN (not COSIGN_PRIVATE_KEY/COSIGN_PASSWORD), so signing failed and blocked the release/preview build — no app shipped first-try.verify-image-provenance is Audit-first (POL-0 Decision 3): unsigned images are reported in a PolicyReport, never blocked at admission. So this makes signing CONDITIONAL: when COSIGN_PRIVATE_KEY is unset/empty the step logs
cosign key not provisioned; skipping signingand continues; when the operator provisions the platform cosign key (cosign-signing-key.yaml + Forgejo Actions secrets) it signs as before — no workflow edit needed to turn it on.Part of the wb-gate capstone release (paired with plat/mitosis#61: germinate CIBTAG 0.2.0 + derive, and lean-trim keeps kyverno/kyverno-policies/letsencrypt/cosign-signing). Validated live on a fresh germination: app builds on ci-builder:0.2.0, cosign step skips gracefully, app ships to a running prod pod (HTTP 200).
Do not merge until the GATE owner merges the release set.