Repository navigation
fix validation during zero-downtime switch - #281
Merged
Merged
Conversation
arttor
requested review from
aiivashchenko,
fa-at-pulsit and
schucly
as code owners
October 27, 2026 10:59
A zero-downtime switch removes the replication policy when it starts, which incorrectly allowed creating conflicting replication policies and changing routing while the switch was in progress. Now validation correctly fails add replication and routing API calls if a zero-downtime switch is in progress. Signed-off-by: Artem Torubarov <artem.torubarov@clyso.com>
arttor
force-pushed
the
tighten-policy-validation-rules
branch
from
October 27, 2026 11:55
09a7131 to
888ed31
Compare
aiivashchenko
approved these changes
Oct 27, 2026
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
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.
A zero-downtime switch removes the replication policy when it starts, which incorrectly allowed creating conflicting replication policies and changing routing while the switch was in progress. Now validation correctly fails add replication and routing API calls if a zero-downtime switch is in progress.