fix: add auth header to wget for private repo download #128
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/westside-landing!128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "226-fix-wget-auth"
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?
Summary
update-kustomize-tagCI step downloadsupdate-kustomize-tag.shfrom pal-e-platform via wget, but gets a 404 because the repo is privateAuthorization: tokenheader using the existingFORGEJO_TOKENsecretChanges
.woodpecker.yaml: added--header="Authorization: token ${FORGEJO_TOKEN}"to the wget command in theupdate-kustomize-tagstepTest Plan
update-kustomize-tagstep downloads the script successfully instead of 404ingReview Checklist
Related Notes
pal-e-platform— the parent repo whose private raw endpoint requires authQA Review
Diff: +1 line, 0 deletions, 1 file changed (
.woodpecker.yaml)Findings
--header="Authorization: token ${FORGEJO_TOKEN}"is the correct Forgejo API token auth format for raw file downloads. Confirmed.FORGEJO_TOKENis already defined in the step'senvironmentblock viafrom_secret: forgejo_token. No new secrets needed.--headerflag is placed between-O /tmp/...and the URL, which is valid wget syntax. Multi-line continuation with indentation matches the existing YAML style.SOP Compliance
VERDICT: APPROVE -- Minimal, correct fix. No issues found.