fix: add auth header to wget for private repo download #235

Merged

forgejo_admin merged 1 commit from 226-fix-wget-auth into main

2026-03-28 16:44:45 +00:00

forgejo_admin commented

2026-03-28 16:31:48 +00:00

Owner

Summary

The update-kustomize-tag CI step downloads update-kustomize-tag.sh from the private pal-e-platform repo via wget, but the request had no authentication, resulting in a 404. This adds an Authorization: token header using the existing FORGEJO_TOKEN secret already available in the step's environment.

Changes

.woodpecker.yaml: Added --header="Authorization: token ${FORGEJO_TOKEN}" to the wget command in the update-kustomize-tag step

Test Plan

Tests pass locally (no test changes — CI-only fix)
Manual verification: next main push pipeline's update-kustomize-tag step succeeds instead of 404ing
No regressions in other pipeline steps

Review Checklist

Passed automated review-fix loop
No secrets committed
No unnecessary file changes
Commit messages are descriptive

Closes forgejo_admin/pal-e-platform#226
pal-e-docs — the project this work belongs to

## Summary The `update-kustomize-tag` CI step downloads `update-kustomize-tag.sh` from the private `pal-e-platform` repo via wget, but the request had no authentication, resulting in a 404. This adds an `Authorization: token` header using the existing `FORGEJO_TOKEN` secret already available in the step's environment. ## Changes - `.woodpecker.yaml`: Added `--header="Authorization: token ${FORGEJO_TOKEN}"` to the wget command in the `update-kustomize-tag` step ## Test Plan - [ ] Tests pass locally (no test changes — CI-only fix) - [ ] Manual verification: next `main` push pipeline's `update-kustomize-tag` step succeeds instead of 404ing - [ ] No regressions in other pipeline steps ## Review Checklist - [ ] Passed automated review-fix loop - [ ] No secrets committed - [ ] No unnecessary file changes - [ ] Commit messages are descriptive ## Related Notes - Closes forgejo_admin/pal-e-platform#226 - `pal-e-docs` — the project this work belongs to

forgejo_admin added 1 commit

2026-03-28 16:31:48 +00:00

fix: add auth header to wget for private repo download e59b2425df

The update-kustomize-tag step downloads a script from the private
pal-e-platform repo but the wget had no auth, causing 404. Add
Authorization header using the existing FORGEJO_TOKEN secret.

Closes forgejo_admin/pal-e-platform#226

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

forgejo_admin commented

2026-03-28 16:32:18 +00:00

Author

Owner

QA Review — PR #235

Scope: 1 file, +1 line, -0 lines. CI-only fix.

Diff Check

The --header="Authorization: token ${FORGEJO_TOKEN}" flag is correctly placed as a continuation line in the multi-line wget command
FORGEJO_TOKEN is already declared in the step's environment block (line 88-89, sourced from forgejo_token secret) — no new secrets or config needed
YAML indentation is consistent with the surrounding continuation lines (10-space indent)
wget accepts flags in any order relative to the URL — placement between -O and the URL is valid

SOP Compliance

PR body has all required sections (Summary, Changes, Test Plan, Review Checklist, Related Notes)
Closes forgejo_admin/pal-e-platform#226 present for cross-repo auto-close
No secrets committed
No unnecessary file changes
Commit message is descriptive

Nits

None.

VERDICT: APPROVE — Clean 1-line fix. The auth header uses the existing secret already available in the step environment.

## QA Review — PR #235 **Scope:** 1 file, +1 line, -0 lines. CI-only fix. ### Diff Check - The `--header="Authorization: token ${FORGEJO_TOKEN}"` flag is correctly placed as a continuation line in the multi-line wget command - `FORGEJO_TOKEN` is already declared in the step's `environment` block (line 88-89, sourced from `forgejo_token` secret) — no new secrets or config needed - YAML indentation is consistent with the surrounding continuation lines (10-space indent) - wget accepts flags in any order relative to the URL — placement between `-O` and the URL is valid ### SOP Compliance - PR body has all required sections (Summary, Changes, Test Plan, Review Checklist, Related Notes) - `Closes forgejo_admin/pal-e-platform#226` present for cross-repo auto-close - No secrets committed - No unnecessary file changes - Commit message is descriptive ### Nits None. --- **VERDICT: APPROVE** — Clean 1-line fix. The auth header uses the existing secret already available in the step environment.