wp-oauth-register.sh: REPO_ROOT computed 1 level too shallow — source fails at runtime #947
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#947
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?
Flagged by AI reviewer in PR #945.
Problem
lib/init/nomad/wp-oauth-register.shline 46 computes REPO_ROOT with only two../levels:But the script lives at
lib/init/nomad/— three levels deep — so../../..is required. Every sibling script in the same directory (vault-engines.sh,vault-nomad-auth.sh,cluster-up.sh,systemd-vault.sh) uses../../...With this bug, REPO_ROOT resolves to
lib/(not the repo root). The subsequentsource "${REPO_ROOT}/lib/hvault.sh"then looks forlib/lib/hvault.sh— a path that does not exist. The script fails at startup.Fix
Auto-created from AI review
Affected files
lib/init/nomad/wp-oauth-register.sh(line 46 — REPO_ROOT path depth)Acceptance criteria
REPO_ROOTinwp-oauth-register.shuses../../..(three levels up), matching all sibling scriptssource "${REPO_ROOT}/lib/hvault.sh"resolves correctly at runtimeshellcheckcleanAlready fixed by #948 —
REPO_ROOTnow correctly uses../../..(line 46). Closing as resolved.