Repository navigation
propose: the deployment's lock moves with the module's ref - #132
Merged
Merged
Conversation
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.
A deployment's plan inits with
-lockfile=readonly, so the pull request Propose opens for #131's module would fail: the module now requiresspin-stack/spin, and the deployment's lock does not have it. Propose now runstofu 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 atf0f9007: init succeeds without AWS credentials and the lock gains exactly thespinprovider block, every platform's hashes.🤖 Generated with Claude Code