Cleanup: remove dead force-unlock retry block from CI apply step #136
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-platform#136
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
plan-pal-e-platform— discovered during QA review of PR #134Repo
forgejo_admin/pal-e-platformWhat Broke
Not broken — dead code. PR #134 added
-lock=falseto bothtofu applycalls. With-lock=false, the "state is already locked" error can never occur, making the force-unlock retry block (.woodpecker.yamllines 148-161) unreachable.Repro Steps
.woodpecker.yamllines 142-161-lock=falseon the initial apply means thegrep -q "the state is already locked"condition is always falseifblock (force-unlock + retry) is dead codeExpected Behavior
Dead code should be removed to keep the pipeline readable. The apply step should be a simple one-liner.
Environment
.woodpecker.yamlAcceptance Criteria
tofu apply -auto-approve -lock=false -no-colorRelated