Auto-init the backend for force-unlock#20
Merged
Merged
Conversation
Running `tf force-unlock <id>` failed with "Backend initialization required, please run terraform init" because force-unlock was not in either of tf's known-subcommand sets, so it fell through to a bare `terraform` invocation with no backend config. Add force-unlock to SUBCOMMANDS_NEEDING_BACKEND so it auto-runs `terraform init` first. Split the var-file injection in TfRunner.call() so it only happens for SUBCOMMANDS_ACCEPTING_VAR_FILE — force-unlock needs the backend wired up but does not accept `-var-file`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
JonJagger
approved these changes
May 27, 2026
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
2 participants
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.
Running
tf force-unlock <id>failed with "Backend initialization required, please run terraform init" because force-unlock was not in either of tf's known-subcommand sets, so it fell through to a bareterraforminvocation with no backend config.Add force-unlock to SUBCOMMANDS_NEEDING_BACKEND so it auto-runs
terraform initfirst. Split the var-file injection in TfRunner.call() so it only happens for SUBCOMMANDS_ACCEPTING_VAR_FILE — force-unlock needs the backend wired up but does not accept-var-file.