Update blackbox probe: westside-app to westside-landing

### Type Feature ### Lineage Sub-ticket of `forgejo_admin/westside-app#109` (Landing site rename — decomposed). Depends on sub-ticket 1 (Forgejo rename). ### Repo `forgejo_admin/pal-e-platform` ### User Story As a superadmin I want the monitoring blackbox probe updated from `westside-app` to `westside-landing` So that uptime monitoring labels match the renamed service identity. ### Context This is sub-ticket 4 of 4 from the decomposed `#109` rename. The blackbox probe in the monitoring module references `westside-app` as the probe name. After rename, this should reflect the new service name for dashboard/alerting consistency. **Note:** The review identified the correct file path as `terraform/modules/monitoring/main.tf` (lines 366-368), NOT `terraform/main.tf` as the parent ticket stated. ### File Targets Files the agent should modify: - `terraform/modules/monitoring/main.tf` — lines 366-368: probe `name = "westside-app"` → `"westside-landing"`, verify `url` and `labels` are consistent Files the agent should NOT touch: - `terraform/main.tf` — only has a `moved` block for keycloak theme, not the blackbox probe - Any other monitoring probes ### Acceptance Criteria - [ ] Blackbox probe name updated from `westside-app` to `westside-landing` - [ ] Probe URL unchanged (still monitors `westsidekingsandqueens.tail5b443a.ts.net`) - [ ] `tofu plan -lock=false` shows only the probe name/label change ### Test Expectations - [ ] `tofu fmt` passes - [ ] `tofu validate` passes - [ ] `tofu plan -lock=false` output shows only expected probe rename - Run command: `cd terraform && tofu plan -lock=false` ### Constraints - `tofu plan -lock=false` before any terraform changes (per `feedback_tofu_lock_false.md`) - Run `tofu fmt` and `tofu validate` before pushing - Depends on sub-ticket 1 (Forgejo rename) completing first - Can proceed in parallel with sub-tickets 2 and 3 after sub-ticket 1 ### Checklist - [ ] PR opened - [ ] `tofu plan` output included in PR - [ ] Tests pass - [ ] No unrelated changes ### Related - `forgejo_admin/westside-app#109` — parent ticket (decomposed) - Sub-ticket 1: Forgejo repo rename (`forgejo_admin/westside-app`) - Sub-ticket 2: pal-e-services terraform updates - Sub-ticket 3: pal-e-deployments overlay updates - `project-westside-basketball`

forgejo_admin commented

2026-03-28 19:09:05 +00:00

Owner

Type

Feature

Lineage

Sub-ticket of forgejo_admin/westside-app#109 (Landing site rename — decomposed). Depends on sub-ticket 1 (Forgejo rename).

Repo

forgejo_admin/pal-e-platform

User Story

As a superadmin
I want the monitoring blackbox probe updated from westside-app to westside-landing
So that uptime monitoring labels match the renamed service identity.

Context

This is sub-ticket 4 of 4 from the decomposed #109 rename. The blackbox probe in the monitoring module references westside-app as the probe name. After rename, this should reflect the new service name for dashboard/alerting consistency.

Note: The review identified the correct file path as terraform/modules/monitoring/main.tf (lines 366-368), NOT terraform/main.tf as the parent ticket stated.

File Targets

Files the agent should modify:

terraform/modules/monitoring/main.tf — lines 366-368: probe name = "westside-app" → "westside-landing", verify url and labels are consistent

Files the agent should NOT touch:

terraform/main.tf — only has a moved block for keycloak theme, not the blackbox probe
Any other monitoring probes

Acceptance Criteria

Blackbox probe name updated from westside-app to westside-landing
Probe URL unchanged (still monitors westsidekingsandqueens.tail5b443a.ts.net)
tofu plan -lock=false shows only the probe name/label change

Test Expectations

tofu fmt passes
tofu validate passes
tofu plan -lock=false output shows only expected probe rename
Run command: cd terraform && tofu plan -lock=false

Constraints

tofu plan -lock=false before any terraform changes (per feedback_tofu_lock_false.md)
Run tofu fmt and tofu validate before pushing
Depends on sub-ticket 1 (Forgejo rename) completing first
Can proceed in parallel with sub-tickets 2 and 3 after sub-ticket 1

Checklist

PR opened
tofu plan output included in PR
Tests pass
No unrelated changes

forgejo_admin/westside-app#109 — parent ticket (decomposed)
Sub-ticket 1: Forgejo repo rename (forgejo_admin/westside-app)
Sub-ticket 2: pal-e-services terraform updates
Sub-ticket 3: pal-e-deployments overlay updates
project-westside-basketball

2026-03-28 19:20:23 +00:00

Author

Scope Review: READY

Review note: review-590-2026-03-28

All 11 template sections present. Traceability complete (story:WS-S26, arch:landing-site). File targets verified -- terraform/modules/monitoring/main.tf lines 366-368 confirmed with exact content match. Acceptance criteria testable via tofu plan. 3 lines in 1 file, well under 5-minute rule.

One sequencing caveat: the probe URL (http://westside-app.westsidekingsandqueens.svc.cluster.local:3000) references the k8s Service DNS name. If ticket #589 (pal-e-deployments) decides to rename the k8s Service, this URL must also change. Recommend dispatching this ticket AFTER #589's scope is finalized.

## Scope Review: READY Review note: `review-590-2026-03-28` All 11 template sections present. Traceability complete (story:WS-S26, arch:landing-site). File targets verified -- `terraform/modules/monitoring/main.tf` lines 366-368 confirmed with exact content match. Acceptance criteria testable via `tofu plan`. 3 lines in 1 file, well under 5-minute rule. One sequencing caveat: the probe URL (`http://westside-app.westsidekingsandqueens.svc.cluster.local:3000`) references the k8s Service DNS name. If ticket #589 (pal-e-deployments) decides to rename the k8s Service, this URL must also change. Recommend dispatching this ticket AFTER #589's scope is finalized.

Rows
Columns

Update blackbox probe: westside-app to westside-landing #229