Let Platform Settings follow the deployment unless you change them #84
Loading…
Reference in a new issue
No description provided.
Delete branch "patrick/settings-follow-deployment"
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?
Platform Settings stored every field on each save, so one save froze the deployment's values of that moment. On Dallas, the Ollama URL and tracing endpoint kept their docker-compose addresses after the chart started setting in-cluster ones: the status page warned about Ollama and Tempo, and no traces reached Tempo.
What changes
Dallas preview (read-only, run in the pod): 46 saved values equal the deployment's own and would be removed, with no change in behaviour (the whole form frozen by one save). Kept: mail.default = sendgrid, from address/name, and API keys only set in the UI. Side benefit: chart-provided secrets (LiveKit, AMI, Reverb) are no longer pinned in the database, so a future rotation in the chart takes effect.
Checked: 7 new tests in PlatformSettingsPageTest; 5 of them fail against the old save code. Full suite: 513 passed, 8 skipped. Pint clean.
🤖 Generated with Claude Code