Today, Modules using valkeymodule-rs can create configs using the valkeymodule macro.
Modules can provide a callback that gets triggered on configuration change (after CONFIG SET).
But we do not have a way for Modules to reject CONFIG SET operations on Module configurations.
In Core valkey, we can do this by having the SDK accept a config_set callback, just like we allow modules to provide a on_configuration_change call back. If the Module returns an Error, the config set operation should be rejected. Else, it can be applied.
Today, Modules using valkeymodule-rs can create configs using the
valkeymodule
macro.Modules can provide a callback that gets triggered on configuration change (after CONFIG SET).
But we do not have a way for Modules to reject CONFIG SET operations on Module configurations.
In Core valkey, we can do this by having the SDK accept a config_set callback, just like we allow modules to provide a on_configuration_change call back. If the Module returns an Error, the config set operation should be rejected. Else, it can be applied.
Current Usage: