Feature Request HyperDX: ConfigMap\Helm connection and source Provisioning #197
Description
Description
Add support for automatically provisioning connections and sources from Kubernetes ConfigMaps or Helm values. This would enable true GitOps workflows and Infrastructure-as-Code management for HyperDX.
The problem:
The defaultConnections\defaultSources values only trigger during initial team creation. There is currently no way to manage or add new sources/connections across existing teams using a GitOps workflow without manual UI steps or updating the DB.
Proposed Solutions:
- Declarative Sync: Allow the backend to read a connection configuration file (YAML/JSON) mounted via a Kubernetes ConfigMap.
- Continuous Reconciliation: The backend should sync/update connections from this file on startup or at a set interval.
- Helm Support: Add a connections block to the Helm values.yaml to allow for native Infrastructure-as-Code management.
Why:
This solution will help the system be more production ready by providing a stable, version-controlled path for configuration that does not rely on fragile direct DB updates.