Conversation
…erts from update certs
Contributor
Contributor
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
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
2 participants
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.
Fixes #2977
Note
Low Risk
Low risk documentation-only change that adds cross-links; potential risk is only incorrect/rotted relrefs across versioned docs.
Overview
Adds a new Prerequisites section to the Redis Software/Enterprise “Update certificates” docs (unversioned,
7.4,7.8,7.22) that explicitly tells users to create replacement certs first and links to the relevant self-signed renewal and CA-signed creation instructions.Reviewed by Cursor Bugbot for commit 26c46a3. Bugbot is set up for automated code reviews on this repo. Configure here.