Configuration overrides

[sam57719]

Can we/should we be able to override/change configuration values in SMIB?

• Through a webpage/api?
• What config should be allowed to be modified?
• What config should be prevented from being modified?

We could utilise pydantic_settings to load overrides from the MongoDB instance

[sjefferson99]

I would expect there to be a number of configuration values that made sense to modify without restarting SMIB if possible (but a container restart isn't the end of the world if it's hard).

I am not sure how that sits with the env file config. In theory if it's set in a file, then it should be updated in that file if adjusted in the web UI or otherwise be expected to be non persistent across reboots.

Do you have a list of possible configs or list of proposed configs that we should perhaps update?

[sam57719]

Currently, the config is loaded into the container as environment variables (from the .env file)

I suggest we store the config overrides in the DB.

SMIB won't start unless the DB is connected, and the DB is persistent between restarts.

I think certainly all the plugin-related configs:

SMIB_PLUGIN_SPACE_STATE_SPACE_OPEN_ANNOUNCE_CHANNEL_ID
SMIB_PLUGIN_STATIC_FILES_STATIC_FILES_DIRECTORY
SMIB_PLUGIN_SMIBHID_SENSOR_MONITOR_INTERVAL
SMIB_PLUGIN_SMIBHID_SENSOR_MONITOR_ALERT_THRESHOLD
SMIB_PLUGIN_SMIBHID_SENSOR_MONITOR_ALERT_RESEND_INTERVAL
SMIB_PLUGIN_SMIBHID_SENSOR_MONITOR_ALERT_CHANNEL_ID

Possibly the log level

SMIB_LOGGING_LOG_LEVEL

Other config values, depending on what they are, could be displayed in a Web UI

[sam57719]

Store in DB or local JSON file.
JSON can be made persistent across restarts using a bind/volume mount
DB is already persistent across restarts, but would require an early connection to DB, which could become messy.

JSON can also be utilised with the existing pydantic_settings