Repository navigation
controlplane: an installation names a release or a channel, and the spin provider resolves it - #131
Merged
Merged
Conversation
…pin provider resolves it spin_version is a release, v<YYYYMMDD>.<N>, or a channel - edge, stable. data.spin_release reads the image catalog (the catalog branch) and answers the release, each role's images by region and the builds its release signed and has not revoked; the module reads them in place of images.json and measurements.json, which go. Upgrading spin no longer moves the module's ref, and a revision or a revocation reaches an installation at its next plan. The catalog's image ids are not what the release signs, its PCRs are, so a released image is asked of the account that publishes Spin OS (image_publisher). Images of your own keep naming an exact release. propose moves the module's ref alone; fresh-install chooses its release from the catalog, and upgrades from the module's newest tag. Closes #130 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aledbf
marked this pull request as ready for review
November 18, 2026 02:25
…l plane The controlplane module requires spin-stack/spin, and lint inits each configuration with -lockfile=readonly: a lock without the provider refused the init. v0.1.0, with the registry's hashes for every platform it serves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aledbf
added a commit
that referenced
this pull request
Nov 18, 2026
A deployment inits its plan with -lockfile=readonly, so a provider the module at the new ref requires and its lock lacks - spin's, since #131 - refused the plan of the very pull request that proposed it. Propose inits the deployment with the pinned OpenTofu after moving the ref: a new provider is recorded, one already locked keeps its version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 4 of #130. Draft until spin-stack/terraform-provider-spin is published to the OpenTofu registry (registry.opentofu.org, which this repo's CI and installations use) and the Terraform registry. Without it,
tofu initcan't findspin-stack/spin, so this PR's CI fails on purpose. Once it's published, a commit here adds the provider's entries to each.terraform.lock.hcl.What changes for an installation
spin_versiontakes a release,v<YYYYMMDD>.<N>, or a channel:edgeorstable. Moving spin no longer moves the module's ref. On a channel, the next plan picks up the new release; a new revision or a revocation shows up the same way.data "spin_release"(providerspin-stack/spin ~> 0.1) replacesimages.jsonandmeasurements.json, and both files are deleted. The provider answers only what the release workflow signed (go-tools'catalog). Anything else fails the plan.data.aws_ami.spin_osnow asks forowners = [var.image_publisher](new variable, default the publishing account277203350136). An id owned by anyone else is not booted. Planted withoutowners, the test fails.image_ids/image_measurementsstill work for images of your own, and thenspin_versionmust be an exact release: a channel would name a release those images don't carry.Scripts
propose.shonly moves the module's ref (spin_versionbelongs to the deployment). The workflow still acceptsregion, because shipset sends it (shipset#22).fresh-install.shpicks the newest release that installs in its region from thecatalogbranch. The upgrade starts from the module's newest tag; a tag from before the catalog upgrades from what its ownimages.jsoninstalls.release.sh's notes sayspin_version = "stable".Checked
tofu testonmodules/controlplane: 65 passed, with the provider built from main through a local filesystem mirror. The image and revocation tests now useoverride_dataondata.spin_release.this: a channel, no image in the region, no trusted build, a revoked release, images of your own on a channel.catalogbranch (created today from main's files, 21 releases, each verified), resolvesv20261114.01to the same runner AMIimages.jsonnames.Merge together with ami's follow-up that drops
images:prand makes the catalog step a failing one: the next release then writes only the catalog. The commit saysCloses #130, but #130 still has the spinbox.dev auto-apply and shipset#22 left: I'll reopen it after the merge.🤖 Generated with Claude Code