Skip to content

Deletes are now idempotent#7266

Merged
ShahabT merged 2 commits intoversioning-3.1-mergefrom
shivam/deletes-idempotent
Feb 6, 2025
Merged

Deletes are now idempotent#7266
ShahabT merged 2 commits intoversioning-3.1-mergefrom
shivam/deletes-idempotent

Conversation

@Shivs11
Copy link
Copy Markdown
Member

@Shivs11 Shivs11 commented Feb 6, 2025

What changed?

  • make deletes idempotent

Why?

How did you test it?

  • added functional tests
  • also changes to functional test to make them have a stricter consistency check

Potential risks

Documentation

Is hotfix candidate?

@Shivs11 Shivs11 requested a review from a team as a code owner February 6, 2025 02:03
Comment on lines +141 to +153

newResp, err := s.FrontendClient().DescribeWorkerDeployment(ctx, &workflowservice.DescribeWorkerDeploymentRequest{
Namespace: s.Namespace().String(),
DeploymentName: tv.DeploymentSeries(),
})
a.NoError(err)

var versionSummaryNames []string
for _, versionSummary := range newResp.GetWorkerDeploymentInfo().GetVersionSummaries() {
versionSummaryNames = append(versionSummaryNames, versionSummary.GetVersion())
}
a.Contains(versionSummaryNames, tv.DeploymentVersionString())

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

this was done because just verifying a version workflow was not enough - we want a strong guarantee in that the deployment workflow should be created + the version should be registered in the deployment workflow's local list

a test was flaking and this fixed it

special thanks to @carlydf for the pair programming session on this one!

@ShahabT ShahabT merged commit f356ee3 into versioning-3.1-merge Feb 6, 2025
@ShahabT ShahabT deleted the shivam/deletes-idempotent branch February 6, 2025 04:02
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- make deletes idempotent

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- added functional tests 
- also changes to functional test to make them have a stricter
consistency check

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- make deletes idempotent

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- added functional tests 
- also changes to functional test to make them have a stricter
consistency check

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- make deletes idempotent

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- added functional tests 
- also changes to functional test to make them have a stricter
consistency check

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
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