Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Revert change to default reapply type" (#5956)
## What changed? Change default `ResetReapply` enum value to `ALL_ELIGIBLE`. ## Why? Reverts #5688, i.e. after this PR we will have the behavior described in #5360. This means both signals *and* updates will be reapplied by default during resets and coinflict resolution, which is the product behavior we want. ### Explanation - #5360 attempted to introduce a new proto enum value and start using it as the default - However, that is not a valid single-deploy change, since it can cause a frontend client on the new version to send a value that is unknown to a history node on the old version. - Therefore #5688 reverted the change to the default, allowing the new proto enum value to be introduced to the codebase - This PR is deployable iff all clusters that we deploy to have #5360 deployed ## How did you test it? I didn't. Tests were added in the original PR #5360. ## Potential risks Could break reset or history conflict resolution. ## Is hotfix candidate? 1.25.1
- Loading branch information