Fix Caddy pillar: wrong Tailscale hostname for landscaping-assistant #444

New issue

Closed

opened 2026-06-16 01:37:27 +00:00 by ldraney · 0 comments

ldraney commented

2026-06-16 01:37:27 +00:00

Owner

Type

Feature

Lineage

Introduced in PR #442 (issue #434). The Caddy pillar data has landscaping.tail5b443a.ts.net but the actual Tailscale machine name is landscaping-assistant. Caddy on the edge-proxy was manually corrected to landscaping-assistant.tail5b443a.ts.net, but the pillar source of truth is wrong.

Repo

ldraney/pal-e-platform

User Story

As a platform operator
I want the Caddy pillar to have the correct Tailscale hostname
So that a future salt state.apply caddy doesn't revert the working config to a broken one

Context

tailscale status shows the machine name is landscaping-assistant, not landscaping. The edge-proxy Caddyfile was manually fixed during deployment validation. The pillar must match to prevent drift.

File Targets

Files the agent should modify:

salt/pillar/caddy.sls — change proxy_target: landscaping.tail5b443a.ts.net to proxy_target: landscaping-assistant.tail5b443a.ts.net

Feature Flag

none

Acceptance Criteria

salt/pillar/caddy.sls has proxy_target: landscaping-assistant.tail5b443a.ts.net for the landscaping site
Rendered Caddyfile matches what is currently deployed on edge-proxy

Test Expectations

Visual diff: one line changed in pillar file

Constraints

One-line fix, keep the PR minimal

Checklist

PR opened
Tests pass
No unrelated changes

ldraney/pal-e-platform #434 — PR #442 that introduced the typo
ldraney/pal-e-platform #440 — pillarization PR that created the pillar structure

### Type Feature ### Lineage Introduced in PR #442 (issue #434). The Caddy pillar data has `landscaping.tail5b443a.ts.net` but the actual Tailscale machine name is `landscaping-assistant`. Caddy on the edge-proxy was manually corrected to `landscaping-assistant.tail5b443a.ts.net`, but the pillar source of truth is wrong. ### Repo `ldraney/pal-e-platform` ### User Story As a platform operator I want the Caddy pillar to have the correct Tailscale hostname So that a future `salt state.apply caddy` doesn't revert the working config to a broken one ### Context `tailscale status` shows the machine name is `landscaping-assistant`, not `landscaping`. The edge-proxy Caddyfile was manually fixed during deployment validation. The pillar must match to prevent drift. ### File Targets Files the agent should modify: - `salt/pillar/caddy.sls` — change `proxy_target: landscaping.tail5b443a.ts.net` to `proxy_target: landscaping-assistant.tail5b443a.ts.net` ### Feature Flag none ### Acceptance Criteria - [ ] `salt/pillar/caddy.sls` has `proxy_target: landscaping-assistant.tail5b443a.ts.net` for the landscaping site - [ ] Rendered Caddyfile matches what is currently deployed on edge-proxy ### Test Expectations - [ ] Visual diff: one line changed in pillar file ### Constraints - One-line fix, keep the PR minimal ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `ldraney/pal-e-platform #434` — PR #442 that introduced the typo - `ldraney/pal-e-platform #440` — pillarization PR that created the pillar structure