Request for Enhanced Dynamic Configuration Support for Core Runtime Settings about dapr HOT 2 OPEN

Hi @yejialiango, thanks for the issue!

You are correct that in order for (all) Dapr services to pick up changes to Configurations, a restart is required. Today, this process is a task left to the reader. There is currently an initiative to make all resources dynamically loadable in Dapr- in v1.13 we added "hot reloading" of Components as a preview feature. The next resource targeted for hot reloading is Subscriptions, targeted for v1.14. Feature requests like these helps us prioritize which resources to work on next, so thank you!

Speculatively, I imagine hot reloading of Configuration would be supported by first listening for SIGHUP signals, and when received, restart the service in-code from main or equivalent. When a Configuration change is detected, the process will send itself this signal. Windows will need to some Go channel or equivalent as it has no SIGHUP. Restarting the service in-code from the top level will be required as values from Configuration span the entire code base so this is the safest/most correct thing to do.

from dapr.

Hi @yejialiango, thanks for the issue!

You are correct that in order for (all) Dapr services to pick up changes to Configurations, a restart is required. Today, this process is a task left to the reader. There is currently an initiative to make all resources dynamically loadable in Dapr- in v1.13 we added "hot reloading" of Components as a preview feature. The next resource targeted for hot reloading is Subscriptions, targeted for v1.14. Feature requests like these helps us prioritize which resources to work on next, so thank you!

Speculatively, I imagine hot reloading of Configuration would be supported by first listening for SIGHUP signals, and when received, restart the service in-code from main or equivalent. When a Configuration change is detected, the process will send itself this signal. Windows will need to some Go channel or equivalent as it has no SIGHUP. Restarting the service in-code from the top level will be required as values from Configuration span the entire code base so this is the safest/most correct thing to do.

Thanks for the quick response and the insights on dynamic loading and hot reloading features. Looking forward to these enhancements in Dapr. I'll explore the core code further and hope to contribute to this area in the future.

from dapr.