mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-09-30 03:01:21 +02:00
A declarative deployment has no way to click through the settings UI, so one provider can be configured entirely from the environment. This reads and defaults only -- validity is decided later by the same OIDCProviderCreate schema the API uses, so env config cannot bypass a check the UI enforces. All four required vars or nothing, and an empty one counts as unset: a provider missing its secret would otherwise be written to the database and fail at authorize time, far from the typo in the compose file that caused it. Booleans follow the project's existing spelling convention (true/1/yes), so an unrecognised value leaves the documented default rather than guessing. Refs #2593