Skip to content

propose: the deployment's lock moves with the module's ref - #132

Merged
aledbf merged 1 commit into
mainfrom
propose-lock
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
propose-lock

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

A deployment's plan inits with -lockfile=readonly, so the pull request Propose opens for #131's module would fail: the module now requires spin-stack/spin, and the deployment's lock does not have it. Propose now runs tofu init -backend=false (the pinned OpenTofu) in the deployment after moving the ref, so a new provider is recorded and one already locked keeps its version.

Checked: task lint; and the step against spinbox.dev-deploy's main at f0f9007: init succeeds without AWS credentials and the lock gains exactly the spin provider block, every platform's hashes.

🤖 Generated with Claude Code

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>
@aledbf
aledbf merged commit 227dfc5 into main Nov 18, 2026
1 check passed
@aledbf
aledbf deleted the propose-lock branch November 18, 2026 12:23
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.

1 participant