Rollout: wire update-kustomize-tag step into all 8 app repos #206
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#206
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
Feature
Lineage
Discovered scope from #204 implementation (PR #205). The reusable script and Woodpecker step template are in pal-e-platform — this ticket covers wiring them into each consumer repo.
Repo
forgejo_admin/pal-e-platform(tracking issue — child work spans 8 repos)User Story
As a platform operator,
I want every app repo to automatically update its kustomize overlay tag after a successful build,
So that deploys are fully automated end-to-end without manual image tag bumps.
Context
PR #205 adds
scripts/update-kustomize-tag.shand a Woodpecker step template. Each app repo needs:update-kustomize-tagstep to.woodpecker.yamlforgejo_tokensecret existspal-e-app specifically: replace brokenDone (PR #67)update-deployment-tagstep that targets wrong repoRollout Status
feedback_archive_mcd_palemail.mdfeedback_archive_mcd_palemail.mdCompleted: 4 of 8 repos.
forgejo_token Audit (Complete)
forgejo_token?Woodpecker Onboarding Prerequisite
westside-contracts and minio-api are not registered in Woodpecker CI. Before the kustomize-tag step can be wired, they need:
.woodpecker.yamlpipeline created (build + push)forgejo_token, registry creds)This is out-of-scope for this issue and requires separate prerequisite tickets.
pal-e-mail Exclusion
pal-e-api Correction
Decisions Needed
Resolved: Exclude mcd-tracker repos. Per feedback_archive_mcd_palemail, mcd-tracker-api and mcd-tracker-app are archive candidates. Do not invest CI onboarding effort in repos headed for archival.
Resolved: Separate prerequisite tickets for Woodpecker onboarding of westside-contracts and minio-api. Each gets its own Forgejo issue covering repo activation, pipeline creation, and secret provisioning. This issue tracks only the kustomize-tag step wiring.
Rollout Order Strategy
File Targets
Per-repo:
.woodpecker.yamlin each app repo.Secret setup: Woodpecker admin UI or
mcp__woodpecker__create_repo_secret.Acceptance Criteria
forgejo_tokensecret provisioned in westside-app and basketball-apiTest Expectations
kubectl get application -n argocdto verify syncConstraints
Depends on #204 (PR #205) being merged firstSatisfied (#204 closed)Checklist
Related
forgejo_admin/pal-e-platform#204— parent issue (closed)board-pal-e-platform— project boardfeedback_archive_mcd_palemail.md— pal-e-mail and mcd-tracker exclusion rationaleRollout Complete
All 4 active repos now have the
update-kustomize-tagWoodpecker step:Secrets provisioned:
forgejo_tokenadded to westside-app and basketball-api.Skipped repos: mcd-tracker-api, mcd-tracker-app, pal-e-mail (archive candidates), westside-contracts and minio-api (not in Woodpecker CI).
Remaining: Verify end-to-end by pushing a trivial change to one repo and confirming the kustomize overlay tag updates automatically.
Scope Review: NEEDS_REFINEMENT
Review note:
review-464-2026-03-27Well-structured tracking issue with correct decomposition strategy (9 child issues, one per repo). Dependency #204 is satisfied (closed). Template is complete with clear acceptance criteria.
Key issues:
scripts/update-kustomize-tag.sh,scripts/woodpecker-update-tag-step.yaml, and all 9 repos confirmed to have.woodpecker.yaml.Issue body updated per scope review corrections.
Scope Review: NEEDS_REFINEMENT
Review note:
review-464-2026-03-27Issue body is stale — 4/8 repos already done on main, acceptance criteria and repo count need updating.
Key issues:
feedback_archive_mcd_palemail.md. Decision needed on inclusion.Decisions needed before moving to next_up:
Body updates needed: repo count, AC progress, audit results, onboarding prerequisites.
Rollout: wire update-kustomize-tag step into all 9 app reposto Rollout: wire update-kustomize-tag step into all 8 app reposScope Review: READY
Review note:
review-464-2026-03-28Re-review after refinement. All 6 prior NEEDS_REFINEMENT items addressed: repo count corrected (8 not 9), rollout status updated (4/8 done), forgejo_token audit complete, Woodpecker onboarding prerequisite documented, mcd-tracker excluded, decisions resolved.
Cosmetic nits (non-blocking):
Ready to move from backlog to todo.