Auto-Reload Configuration on Detection of File and SSV loader Detection Changes
Description
I would like cb able to automatically reload the configuration when it detects changes in either the configuration file (cb-config.toml) and the SSV node operator status (e.g., when a new validator key becomes active or added in the SSV network). This would streamline the process for newly deposited/activated validator keys without requiring manual hot reloads via a POST request to the /reload endpoint.
Current Behavior
- A manual hot reload (via a POST request to
/reload) is required to apply the updated configuration for the new key to enable the mux option. If no hot reload is performed, the key uses the default relay list (no mux).
- cb dose not detect changes in the SSV node operator change automatically.
Auto-Reload Configuration on Detection of File and SSV loader Detection Changes
Description
I would like cb able to automatically reload the configuration when it detects changes in either the configuration file (
cb-config.toml) and the SSV node operator status (e.g., when a new validator key becomes active or added in the SSV network). This would streamline the process for newly deposited/activated validator keys without requiring manual hot reloads via a POST request to the/reloadendpoint.Current Behavior
/reload) is required to apply the updated configuration for the new key to enable the mux option. If no hot reload is performed, the key uses the default relay list (no mux).