Skip to content

Added RM_GetInternalSecret to redismodule.h#407

Merged
MeirShpilraien merged 2 commits intomasterfrom
add_GetInternalSecret_redismodule_api
Feb 5, 2025
Merged

Added RM_GetInternalSecret to redismodule.h#407
MeirShpilraien merged 2 commits intomasterfrom
add_GetInternalSecret_redismodule_api

Conversation

@MeirShpilraien
Copy link

Added the new API, RedisModule_GetInternalSecret, introduce on redis/redis#13740 to redismodule.h.

@MeirShpilraien MeirShpilraien merged commit b5b359e into master Feb 5, 2025
16 checks passed
@MeirShpilraien MeirShpilraien deleted the add_GetInternalSecret_redismodule_api branch February 5, 2025 10:20
MeirShpilraien pushed a commit to RedisGears/LibMR that referenced this pull request Feb 5, 2025
The PR makes changes to use the internal command capabilities introduced on: redis/redis#13740.
The main idea is to use the new redismodule API that provides internal secret for internal shard communication.

This means that the following is no longer needed:
1. The new user configuration.
2. The internal ACL category

All the commands are marked with the `internal` flag (if we see that the internal commands feature is supported on the current Redis version we run on). In addition, the connection between the shards uses `INTERNALAUTH` with the given internal secret so it can run all the internal commands. Regular user can not run any internal command.

The PR require the following PR's to be merge:
1. redis/redis#13740
2. RedisLabsModules/redismodule-rs#407

The tests was modified to avoid giving password to the test module in case it detects that the internal commands feature exists. In such case, avoiding giving the password to the module, make sure that LibMR actually using the `INTERNALAUTH` command with the internal secret to authenticate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants