Skip to content

spin_release: a release or channel, its images and the builds its release signed - #2

Merged
aledbf merged 2 commits into
mainfrom
spin-release
Nov 17, 2026
Merged

aledbf merged 2 commits into
mainfrom
spin-release

Conversation

@aledbf

@aledbf aledbf commented Nov 17, 2026

Copy link
Copy Markdown
Member

Closes #1. Part 3 of spin-stack/spin-terraform-aws#130.

data "spin_release" { version = "edge" | "stable" | "v<YYYYMMDD>.<N>" } reads the image catalog (spin-terraform-aws's catalog branch, or catalog_url's mirror). It answers:

  • release: the release named, or the one the channel names now;
  • images: role → region → AMI, the newest build's;
  • revisions: role → its newest build, r<N>;
  • builds: role → the builds not revoked, oldest first, each with pcr4/pcr7/pcr12 and the statement + bundle in base64, which is how the modules hand them to the control plane today;
  • revoked: role → why, when its newest build is revoked.

Everything goes through go-tools' catalog.Verify/VerifyChannel against catalog.Signers() (ami's release/revoke/promote workflows on main, under go-tools' pinned Sigstore root). Anything unsigned, forged, missing or oversized fails the plan; nothing partial is answered.

Tests: internal/resolve with an httptest catalog (forged PCR, unsigned channel, missing release or channel, a channel naming a missing release, oversized file, upstream errors). internal/provider runs real configurations under OpenTofu (terraform-plugin-testing), and the CI installs OpenTofu so they don't skip. go-tools' mutate: 0 survived.

Publishing to registry.terraform.io is yours. release.yml (GoReleaser on a v* tag) needs a GPG key: its private half in the GPG_PRIVATE_KEY and PASSPHRASE secrets, its public half added to spin-stack's signing keys in the registry, and the org signed in to the registry. Until then, the module can use it through a filesystem mirror or dev_overrides.

No licence file: that is your call (open in the licence decision).

🤖 Generated with Claude Code

aledbf and others added 2 commits November 17, 2026 13:40
…ease signed

An installation names a spin release or a channel and nothing else
(spin-stack/spin-terraform-aws#130). This reads it from the image
catalog and answers each role's images by region, its newest revision,
the builds a machine of it may prove it booted, and why a newest build
is revoked - believed only as go-tools' catalog verifies it against the
release workflow's signatures, or the plan fails.

Closes #1

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit a99e6fd into main Nov 17, 2026
1 check passed
@aledbf
aledbf deleted the spin-release branch November 17, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

data "spin_release": a release or channel, its images and verified builds

1 participant