Commit 6ced521
chore(tra-974): drop dead BACKEND_LOG_LEVEL key from backend chart
The trakrf-backend logger reads bare LOG_LEVEL via os.Getenv
(logger/config.go) — there is no BACKEND_ prefix scheme, so the chart's
config.logLevel → BACKEND_LOG_LEVEL ConfigMap key was never read by the
backend (confirmed against the backend source). PR #157 added the real
LOG_LEVEL emission (config.runtimeLogLevel); this removes the misleading
dead key and its now-orphaned config.logLevel value so the chart is honest.
No functional change — BACKEND_LOG_LEVEL was inert. Removing it does change
both envs' rendered ConfigMap (key drops out), so the next apply-root-app.sh
gke rolls the prod backend pod once (clean restart, no behavior change);
preview keeps LOG_LEVEL=info via config.runtimeLogLevel.
Verified via helm template: BACKEND_LOG_LEVEL absent from all renders;
LOG_LEVEL=info still emits when runtimeLogLevel is set; chart renders clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent 2f1e000 commit 6ced521
2 files changed
Lines changed: 6 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
10 | | - | |
11 | 10 | | |
12 | | - | |
13 | | - | |
14 | | - | |
15 | | - | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
16 | 14 | | |
17 | 15 | | |
18 | 16 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
142 | | - | |
143 | 142 | | |
144 | | - | |
145 | | - | |
146 | | - | |
147 | | - | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
148 | 146 | | |
149 | 147 | | |
150 | 148 | | |
| |||
0 commit comments