[codex] Clarify supported Redis paths for EDU-1130#1298
Draft
llewellyn-sl wants to merge 2 commits intomasterfrom
Draft
[codex] Clarify supported Redis paths for EDU-1130#1298llewellyn-sl wants to merge 2 commits intomasterfrom
llewellyn-sl wants to merge 2 commits intomasterfrom
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
Summary
This draft makes the supported Redis deployment paths explicit for current Platform Enterprise installs so operators can quickly distinguish the documented production options from unlisted Redis-compatible alternatives.
Source context
Repo and doc targets
seqeralabs/docsplatform-enterprise_versioned_docsversion-25.3/enterprise/install-platform.mdversion-25.3/enterprise/configuration/overview.mdxRationale
The EDU signal here was not a confirmed product statement that Valkey is supported or unsupported. The actionable docs gap was that the current pages make the supported Redis path too implicit during planning. This draft tightens that by naming the documented production options and by telling operators to confirm support before using another Redis-compatible service in production.
Validation
markdownlint-cli2on the touched files with a temporary npm cache.Follow-up
Please confirm whether product wants a stronger explicit statement about Valkey compatibility status, or whether the current support-boundary wording is preferred until that position is formalized.