Support for Live Config Reload with Request-Level Isolation

[LutherLee]

Hi,

I was wondering if this feature is supported?

Description:
This feature enables dynamic updating of configuration values at runtime without requiring a server restart. When a config value (such as an environment variable or application setting) is updated, the new value is immediately available for new incoming requests, while existing requests continue to use the value that was current at the time they started. This ensures stability for in-flight operations while allowing real-time reconfiguration of the system.

Key Benefits:

1. Zero Downtime Updates: Apply configuration changes without restarting the server.
2. Request-Level Isolation: Active requests are not affected by mid-execution config changes.
3. Seamless Integration: Compatible with standard Go patterns and concurrency-safe.

Example Use Cases:

• Toggling feature flags without downtime
• Adjusting rate limits or timeouts on-the-fly
• Rotating keys or secrets used in future requests

[chaindead]

Thx for issue, but live-reload conflicting with project internal structure. If you have ideas how to implement it, would be great, but for now this feature is not prioritized

viper is good at live reload as far as i know