Service command-line configuration dialog with bitemporal support
Table of Contents
This page is a capture in the next bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
(One paragraph: the idea.)
Why
(Motivation, problem being solved, related context.)
References
See also
Operators currently change service command-line options (log level, telemetry endpoint, feature flags) by editing start scripts and restarting the service. Instead:
- Add a
ores_infra_service_configs_tblwith bitemporal + audit columns storing per-service parameter overrides. - Seed it at database setup with defaults.
- Add a "Service Configuration" dialog in the admin area of the Qt app: select a service, edit its parameters, save.
- The service reads its effective config on startup (or on a NATS signal) from the database, merging with CLI defaults.
Bitemporal support means operators can see who changed what and when, and roll back to a previous configuration.