Yuneng Jiang 7353b779c2 feat(proxy): say when a stored setting is ignored because the config file owns it ... The config file winning over the database was silent. An admin who had set a value through the UI and later pinned the same key in the file saw their stored value quietly stop applying, with nothing said at boot and nothing said when a later write was refused. Startup now warns once per key whose stored value differs from the file's, naming the key and what to do about it. The refusal raised on a write to a config-owned key carries the same sentence, so the log and the 400 read identically, and both call out that a stored value exists and will never be applied. The /config/update refusal gained the same detail. Keys the file does not declare are untouched: the database still owns them, and a stored value equal to the file's is not worth a warning.		2026-09-19 10:20:31 -07:00
..
test_config_resolvers.py	feat(proxy): add SAML 2.0 SSO for the admin UI (#31429)	2026-07-24 12:51:28 -07:00
test_settings_rules.py	fix(proxy): refuse config-owned writes at one choke point and refresh the store	2026-09-18 01:49:30 -07:00
test_settings_store.py	feat(proxy): say when a stored setting is ignored because the config file owns it	2026-09-19 10:20:31 -07:00