pal-e-docs

Validation: pal-e-production → pal-e-app rename

validation-114-2026-04-12 Doc

validation pass
Project

Validation: pal-e-production → pal-e-app rename (#114)

Verdict: PASS

Acceptance Criteria

Criteria Status Evidence
Forgejo repo at forgejo_admin/pal-e-app PASS API rename returned 200, URL accessible
k8s namespace pal-e-app with running pod PASS kubectl: 1/1 Running
https://pal-e-app.tail5b443a.ts.net returns 200 PASS curl: HTTP/2 200, content-type text/html
ArgoCD synced + healthy PASS Synced Healthy
Monitoring probe renamed PASS PR #287 merged — probe name + labels updated
Network policies reference pal-e-app PASS PR #287 merged — lines 172, 196 updated
Golden signals dashboard renamed PASS PR #287 merged — file renamed, 14+ PromQL refs updated
Local remote updated PASS ~/pal-e-app origin → forgejo_admin/pal-e-app.git

PRs Merged

  • pal-e-deployments#120 — new kustomize overlay
  • pal-e-deployments#121 — SOPS harbor-creds (initial)
  • pal-e-deployments#122 — fix harbor-creds password
  • pal-e-deployments#123 — fix harbor-creds username (bash $ expansion)
  • pal-e-platform#287 — monitoring + network policies + dashboard

Issues Encountered

  • SOPS harbor-creds had wrong username: bash $ expansion turned robot$pal-e-app into ldraney. Fixed by generating YAML with Python.
  • Harbor image was OCI format — containerd HEAD request got 404 misread as 401. Fixed with skopeo copy --format v2s2 (OCI → Docker manifest).
  • Terraform state drift: pal-e-production robots not in state, blocking applies. Resolved by removing pal-e-production from tfvars.
  • Overlay directory was pal-e-docs-app not pal-e-production — previous rename never completed at directory level.

Remaining Cleanup

  • Old overlays/pal-e-docs-app/ directory still in pal-e-deployments — can be deleted in a future PR
  • CORS env var PALDOCS_ALLOWED_ORIGINS on pal-e-docs deployment needs updating to include https://pal-e-app.tail5b443a.ts.net
  • Woodpecker CI webhook needs verification on next push to renamed repo
  • Board items #979, #980 have Forgejo URLs pointing to old repo name (auto-redirected by Forgejo)