fix: rename westside-landing → westside-app in monitoring probe #281
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!281
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "208-rename-westside-landing-monitoring"
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
Renames the blackbox exporter probe from
westside-landingtowestside-appto align with the repo rename.Changes
terraform/modules/monitoring/main.tf— updated probenameandservicelabel fromwestside-landingtowestside-appTest Plan
grep westside-landing terraform/modules/monitoring/main.tfreturns no matchestofu apply, verify the blackbox probe target appears aswestside-appin PrometheusReview Checklist
grep westside-landingreturns nothing in the changed filewestside-landingin monitoring contextRelated Notes
Related
PR #281 Review
DOMAIN REVIEW
Tech stack: Terraform (HCL) -- Helm release values for blackbox exporter probes.
The actual Terraform change is a clean 2-line rename:
namefield:westside-landing->westside-applabels.service:westside-landing->westside-appThe probe URL (
http://westside-app.westsidekingsandqueens.svc.cluster.local:3000) was already correct and did not need changing. The rename aligns the probe name and service label with the current repo/service name. Notofu fmtor validation concerns -- this is a string value change only.BLOCKERS
1. Unrelated file committed:
docs/superpowers/specs/2026-04-10-westside-admin-design.md(183 lines added)This is a full design spec for a new
westside-adminproject. It has zero relationship to renaming a monitoring probe fromwestside-landingtowestside-app. This is textbook scope creep -- an unrelated 183-line document riding alongside a 2-line fix.This file must be removed from this branch before merge. If it belongs in the repo, it should arrive via its own PR with its own issue reference.
NITS
None. The actual Terraform change is minimal and correct.
SOP COMPLIANCE
208-rename-westside-landing-monitoringreferences issue #208forgejo_admin/westside-landing#208)docs/superpowers/specs/2026-04-10-westside-admin-design.mdis unrelated scope creepPROCESS OBSERVATIONS
Low-risk rename. Change failure risk is near zero for the actual Terraform diff. The stowaway design spec is the only problem -- it inflates the PR from 2 changed lines to 185 additions, obscuring the actual change and violating scope discipline. Keeping PRs atomic is critical for DORA change failure rate.
VERDICT: NOT APPROVED
Remove
docs/superpowers/specs/2026-04-10-westside-admin-design.mdfrom this branch. The 2-line monitoring rename is good to go once the unrelated file is dropped.dab59f48b024fbf98cebPR #281 Review (Re-review)
DOMAIN REVIEW
Tech stack: Terraform/HCL (Helm release values for blackbox exporter)
The change renames the blackbox probe
nameandservicelabel fromwestside-landingtowestside-app, aligning with the repo rename. Two observations:urlfield already pointed towestside-app.westsidekingsandqueens.svc.cluster.local:3000before this PR -- only the metadata labels were stale. This PR completes the rename correctly.westside-landing. The only remaining hits are in an untracked design spec (docs/superpowers/specs/) and.claude/worktrees/artifacts -- neither is in scope.No
tofu fmtortofu validateconcerns with a simple string rename. No state-breaking changes -- this modifies Helm release values, not resource addresses.BLOCKERS
None.
NITS
None. The previous review's blocker (stray design spec file) has been resolved by the force-push rebase. The diff now contains exactly the 2-line change described in the PR body.
SOP COMPLIANCE
208-rename-westside-landing-monitoring)forgejo_admin/westside-landing#208PROCESS OBSERVATIONS
Clean re-review. The force-push rebase removed the stray file cleanly. Low change-failure risk -- metadata-only rename with no functional impact until
tofu applypropagates the new labels to Prometheus.VERDICT: APPROVED