Update
Move the module’s ref to a release of spin-terraform-aws - or a commit - whose images.json has
the new spin release in the installation’s region, change spin_version in terraform.tfvars to
it, then:
tofu plan # the image, the launch templates and the documents change, and nothing elsetofu applyspin-terraform-aws has releases of its own, v<YYYYMMDD>.<NN> tags a person cuts from main
(gh workflow run release.yml --ref main, which names the next one today):
an installation that pins one (?ref=v<YYYYMMDD>.<NN>) gets an update when somebody decides this
module - its shapes and the images its images.json has - is ready for it, not when main moves.
The newest is the first on its releases.
main is what spin-stack’s own installation, spinbox.dev, runs first.
For the installations spin-stack runs, that edit is a pull request nobody writes, and every step
of it is a workflow run, with its log: spin-stack/shipset, which coordinates them, dispatches
spin-stack/ami’s release workflow for each spin release, which builds and publishes its image and
opens the pull request that adds it to spin-terraform-aws’s images.json; shipset merges that
once its checks pass, and dispatches spin-terraform-aws’s .github/workflows/propose.yml for each
deployment its shipset.yaml names - on main for one that follows main, on the newest release’s
tag for one that follows the releases - which opens, or rewrites, the pull request there that moves both. A person merges that, and
applies.
The control plane and the proxy are each replaced beside themselves. The old proxy serves until the
new one does. The control plane’s database has one writer, so the old control plane serves until
the new one asks for it, then archives what it wrote and stops: the installation has no control
plane until the new one has restored the database and started - seconds, which spin waits out
for a read and a workspace does not notice. How it went is tofu output update_status:
InProgress, Successful, or RollbackSuccessful with the reason. A new control plane that
failed before it asked for the database leaves the old one serving; one that failed after hands the name back, and
the old machine’s watch starts its control plane within a minute, which restores the database from
the archive first - or takes the name back after fifteen minutes when the new machine died without
handing it. tofu output boot_log - one command per role, since a role’s machines are one stream prefix - says
why the new one did not come up. Until the launch hook gives up on a new machine that never comes
up, the refresh holds the group and an apply that changes it is refused; tofu output update_abort,
by group, is the command that rolls it back now. A change to anything else a machine starts on -
installation_config, the autoscaling settings, the control plane’s or the proxy’s instance
type - rolls out the same way. A change to a machine’s document alone reaches it when it next starts; to start one now:
aws autoscaling start-instance-refresh --auto-scaling-group-name <group>A runner cannot take a release in place either - its root is read-only and verified - and how it
gets one is runner_rollout. idle, the default, moves no workspace for it: the control plane
empties the group once nothing runs, starts or is still being saved to the bucket, and the next
host it starts boots the new release; until then a host keeps the old one, which its control plane
serves for 90 days (spin’s compat.Window). rolling is for a fleet that never empties: the hosts
are replaced at once, one at a time with the new one first, each old one leaving by its drain - its
workspaces suspended to the bucket and resumed on another host.
A release older than the one that last started the database refuses to start on it: going back past a change to the schema is a restore of the database from its archive to a point before it, not an update.
Generated by task reference from spin-terraform-aws/README.md at 358445c95.
Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.

