warning in Standalone Replica Clusters - #145
Closed
cod3mas0n wants to merge 2 commits into
Closed
Conversation
… to be more explicit Signed-off-by: Ali Mehraji <a.mehraji75@gmail.com>
Author
|
I will submit a PR for the cloudnative-pg repo, so I'm closing this one. |
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.
Fix the wording in the warning for standalone replica clusters.
The current text refers to the “designated primary” being promoted to primary, which can be misleading because the operation is performed on the replica cluster.
Update the wording to make this distinction clear and avoid confusion between the source cluster's primary and the primary instance within the replica cluster.