Port config callbacks to Redis 8 module API

[bigmountainben]

Summary

• Strip a leading <prefix>. in every RedisRaftConfig getter/setter so the callbacks work against both Redis ≤ 8.3 (unprefixed "<name>") and Redis 8.4+, where setModuleEnumConfig passes the prefixed "raft.<name>" to the callback while the bool/string/numeric setters still pass the unprefixed form.
• Move sc_list_init(&rr->blocked_command_list) ahead of ConfigInit() in RedisRaftCtxInit() so the list is initialized before any registered config callback can run during registration.

Background

In Redis 8.4 the module config plumbing was tightened: setModuleEnumConfig now hands the callback the full "<module-prefix>.<name>" it was registered under, while the other typed setters continue to pass the bare "<name>". The existing strcasecmp(name, conf_*) chains in src/config.c matched the bare form only, so any CONFIG SET raft.trace ... (or raft.loglevel) on Redis 8.4 would silently fall through.

The fix is a one-liner per callback (name = stripConfPrefix(name);) that normalizes both forms; no API signatures change and pre-8.4 builds are unaffected.

Test plan

• Build against Redis 8.4 and run the integration suite.
• CONFIG SET raft.trace node and CONFIG SET raft.loglevel debug round-trip via CONFIG GET on Redis 8.4.
• CONFIG SET raft.log-fsync no (bool), CONFIG SET raft.addr 127.0.0.1:5001 (string), CONFIG SET raft.periodic-interval 200 (numeric) all still apply on Redis 8.4.
• Same commands still work against an older Redis (≤ 8.3) build to confirm no regression.
• Module loads cleanly with config options supplied at load time (so the setter callbacks fire before RedisRaftCtxInit() completes — verifies the blocked_command_list init reorder).

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.