Repository navigation
Namespace Rabbit Redis keys for shared instances - #32
Merged
Merged
Conversation
Signed-off-by: theboringhumane <me@iamharsh.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rabbit currently writes generic
session:*andport_lock:*keys, which prevents a narrow service namespace when sharing Redis. AddRABBIT_REDIS_KEY_PREFIXto namespace all cache, session, counter and lock keys, including owner-safe Lua release. Empty configuration preserves existing keys.The prefix accepts 2–128 ASCII characters, starts with a letter or digit, ends with
:, and rejects ACL glob patterns and escapes before either database connection starts. The shared Redis guide covers ACL commands, verified TLS and coordinated prefix changes.Validation on the dedicated Linux VM: full server tests, database tests with the race detector, vet and server build. Real disposable Redis/PostgreSQL tests cover legacy keys, independent prefixes, foreign-key and Lua ACL denials, token allocation, sessions and scoped revocation. CI requires the two new live gates to pass. Owned fixture cleanup is verified separately.