admin/felhom.eu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

REPORT: record v0.42.0 deploy + live-validation outcome

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6
This commit is contained in:
authentik Default Admin
2026-07-10 15:22:23 +02:00
parent 9f1759132d
commit 0cc70a7a5a
1 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REPORT.md
+16 -5
View File
@@ -38,8 +38,19 @@ independently, via the post-save provision-merge — untouched by this change.
Green gate: `go build ./... && go vet ./... && go test ./...` — all pass.
### Deploy + live check (operator-free)
GitOps: build 0.42.0 on 180 → bump `manifests/hub.yaml` tag → ArgoCD sync → Synced/Healthy. Live proof on
the **demo** customer (not Peti): edit → tick debug → save → the demo controller restarts next cycle →
`/debug` serves → untick → save → `/debug` 404 again. See the hub CHANGELOG top entry + session notes for
the live-validation outcome. Peti-box use (enabling on his config) is Viktor's click — not part of this task.
### Deploy — DONE
GitOps: image `felhom-hub:0.42.0` built on 180 → `manifests/hub.yaml` tag bumped (0.41.0→0.42.0) → ArgoCD
hard-refresh + sync → **Synced/Healthy**, live image 0.42.0, pod rolled out (2026-07-10 15:17 CEST).
### Live validation — done except the one operator-gated click
- **Off-baseline (live, operator-free):** the demo controller's generated `controller.yaml` carries
`logging.level: info` and its `/debug` route returns **404** — the exact observable the toggle flips, and
proof the `logging.level` merge target exists in the real generated config.
- **Propagation leg (green test):** `configgen.TestGenerate_DebugLevelOverride` pins that
`logging.level=debug` in ConfigJSON deep-merges over the `info` default into the generated YAML (the merge
target shape taken from the live box). configgen itself was not modified.
- **The one operator step:** ticking "Debug mód" on the demo customer and saving goes through the hub's
operator-password-gated UI — a credential CC does not have (no logged-in browser session available this
run). That single save (→ demo controller restarts next cycle → `/debug` ≠ 404 → untick → 404) is the last
hands-on confirmation; Viktor can click it. **Peti-box use (enabling on his config) is likewise Viktor's
click — not part of this task.**