Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slack-vitess-r15.0.5: add slack_cross_cell custom durability policy #266

Merged

Conversation

timvaillancourt
Copy link
Member

@timvaillancourt timvaillancourt commented Mar 21, 2024

Description

This PR adds the custom slack_cross_cell Durability Policy to our v15 release to allow the flexibility in promotion rules and semi-sync ackers that we expect with our deployment today

The durability policy code was added to a new, private repo so it can be stored independent to this code: https://github.com/slackhq/vitess-addons/tree/v0.15.3/go/durability

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
@github-actions github-actions bot added this to the v15.0.5 milestone Mar 21, 2024
@timvaillancourt timvaillancourt changed the title slack-vitess-r15.0.5: add slack_cross_cell custom durability policy slack-vitess-r15.0.5: add slack_cross_cell custom durability policy Mar 21, 2024
timvaillancourt and others added 5 commits March 22, 2024 00:57
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Manan Gupta <[email protected]>
Co-authored-by: Manan Gupta <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
timvaillancourt and others added 12 commits April 8, 2024 15:47
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
* Update all the Go dependencies

This seems to work for the basics just fine, so let's have CI take a run
at this as well to update these.

Only one small update to the Azure blob storage handling seems needed so
far.

Signed-off-by: Dirkjan Bussink <[email protected]>

* Use correct proto comparisons

We're using `reflect.DeepEqual` or `testify` helpers that essentially
use that in a number of places are comparing protobufs. This is not
supported though, protobufs are not comparable with `reflect.DeepEqual`.

This is exposed because of the tiny patch bump of protobuf which changes
some internal optimization of how it initializes protobufs that breaks
all this.

Instead, move to the appropriate helpers here.

Signed-off-by: Dirkjan Bussink <[email protected]>

Signed-off-by: Dirkjan Bussink <[email protected]>
Copy link

salesforce-cla bot commented Apr 8, 2024

Thanks for the contribution! Before we can merge this, we need @dbussink to sign the Salesforce Inc. Contributor License Agreement.

Signed-off-by: Tim Vaillancourt <[email protected]>
@timvaillancourt timvaillancourt marked this pull request as ready for review May 16, 2024 17:36
@timvaillancourt timvaillancourt requested a review from a team as a code owner May 16, 2024 17:36
@timvaillancourt timvaillancourt merged commit a912583 into slack-vitess-r15.0.5 May 22, 2024
196 of 197 checks passed
@timvaillancourt timvaillancourt deleted the slack_cross_cell-slack-vitess-r15.0.5 branch May 22, 2024 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants