docs(ci): register westside-admin in overlay-mapping header (#312) #313
No reviewers
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
ldraney/pal-e-platform!313
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "register-westside-admin-overlay"
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
Adds a single comment line registering
westside-admin -> OVERLAY=westside-admininscripts/woodpecker-update-tag-step.yaml's overlay-mapping header.Why
Wave 2B's
.woodpecker.yaml(westside-admin#11, merged) consumes this shared script withOVERLAY=westside-admin. The script's runtime behavior already supports any OVERLAY value passed in — this PR only updates the documentation header so future agents/operators can discover that westside-admin has an active overlay in pal-e-deployments.Changes
scripts/woodpecker-update-tag-step.yaml— one new comment line registeringwestside-admin -> OVERLAY=westside-adminbetween westside-app and basketball-api in the overlay-mapping headerTest Plan
grep westside-admin scripts/woodpecker-update-tag-step.yamlreturns the new lineOVERLAYenv var at runtime, doesn't parse the headerReview Checklist
story:admin-row-crud,arch:ci-pipeline)Related Notes
feedback_discovered_scope_always_trackedconvention-architecture-ids(overlay naming)Closes #312
PR #313 Review
DOMAIN REVIEW
Stack: Woodpecker CI shared YAML step (documentation header only).
Single-line comment addition at line 8, registering
westside-admin -> OVERLAY=westside-adminbetweenwestside-app(line 7) andbasketball-api(line 9). Alphabetical-ish/insertion ordering preserved with the existing pattern (related westside services grouped at top). Column alignment matches surrounding entries (22-char service column,-> OVERLAY=separator).The script's runtime behavior is unaffected —
OVERLAYis supplied at line 30 from the consuming.woodpecker.yamlenv block. The header is pure operator documentation.BLOCKERS
None.
NITS
None. The line slots cleanly into the existing block and matches column width.
SOP COMPLIANCE
register-westside-admin-overlay(descriptive; missing issue number prefix per{issue-number}-{kebab}convention, but consistent with prior register-* docs PRs in this repo)Closes #312presentstory:admin-row-crud,arch:ci-pipelinePROCESS OBSERVATIONS
Textbook discovered-scope hygiene: Wave 2B QA flagged the missing registry entry on westside-admin#11, a new ticket (#312) was filed, and this PR closes it with the smallest possible change. Zero deployment risk (CI script reads env at runtime, doesn't parse the comment). DF impact: positive — removes a future onboarding speedbump for operators reading the script header. CFR: zero.
Minor branch-naming nit only; not a blocker.
VERDICT: APPROVED