Rename is_replication_enabled to enable_replication#676
Merged
michaely520 merged 2 commits intomasterfrom Dec 3, 2025
Merged
Conversation
cretz
approved these changes
Dec 2, 2025
bergundy
approved these changes
Dec 3, 2025
Member
bergundy
left a comment
bergundy
left a comment
There was a problem hiding this comment.
Approving assuming that this field was never referenced in our codebase.
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
3 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.
What changed?
Renaming field to be consistent with enable_remote_cluster_connection from #672
Why?
CLI experience/readability headache to have inconsistency
Breaking changes
should be ok, field is new and unused
Server PR
na