Skip to content

Rename is_replication_enabled to enable_replication - #676

Merged
michaely520 merged 2 commits into
masterfrom
fix-rename
Dec 3, 2025
Merged

Rename is_replication_enabled to enable_replication#676
michaely520 merged 2 commits into
masterfrom
fix-rename

Conversation

@michaely520

@michaely520 michaely520 commented Dec 2, 2025

Copy link
Copy Markdown
Contributor

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

@michaely520
michaely520 requested review from a team as code owners December 2, 2025 20:22

@bergundy bergundy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving assuming that this field was never referenced in our codebase.

@michaely520
michaely520 merged commit 31333b1 into master Dec 3, 2025
4 checks passed
@michaely520
michaely520 deleted the fix-rename branch December 3, 2025 00:27
stephanos pushed a commit that referenced this pull request Mar 10, 2026
<!-- Describe what has changed in this PR -->
**What changed?**
Renaming field to be consistent with enable_remote_cluster_connection
from #672

<!-- Tell your future self why have you made these changes -->
**Why?**
CLI experience/readability headache to have inconsistency

<!-- Are there any breaking changes on binary or code level? -->
**Breaking changes**
should be ok, field is new and unused

<!-- If this breaks the Server, please provide the Server PR to merge
right after this PR was merged. -->
**Server PR**
na
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants