Skip to content

Delete Namespace: fix incompatible change in reclaim resources workflow#7385

Merged
alexshtin merged 1 commit intotemporalio:mainfrom
alexshtin:fix/delete-ns-reclaim-res-nde
Feb 26, 2025
Merged

Delete Namespace: fix incompatible change in reclaim resources workflow#7385
alexshtin merged 1 commit intotemporalio:mainfrom
alexshtin:fix/delete-ns-reclaim-res-nde

Conversation

@alexshtin
Copy link
Contributor

@alexshtin alexshtin commented Feb 25, 2025

What changed?

#7215 introduced incompatible change in reclaim resources workflow code (extra local activity call). If new version is rolled out while previous workflow is running, it will generate NDE. This PR adds proper version check (patch API) to avoid it.

Why?

Bug fix.

How did you test it?

Run upgrade locally.

Potential risks

No risks.

Documentation

No.

Is hotfix candidate?

Yes.

@alexshtin alexshtin requested a review from a team as a code owner February 25, 2025 20:04
if err != nil {
return result, err
// TODO: remove version check and 9s const after v1.27 release.
namespaceCacheRefreshDelay := 9 * time.Second
Copy link
Contributor

Choose a reason for hiding this comment

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

🪄 Magic number

@alexshtin alexshtin merged commit 9c7d332 into temporalio:main Feb 26, 2025
49 checks passed
@alexshtin alexshtin deleted the fix/delete-ns-reclaim-res-nde branch February 26, 2025 00:28
rodrigozhou pushed a commit that referenced this pull request Feb 26, 2025
…ow (#7385)

## What changed?
<!-- Describe what has changed in this PR -->
#7215 introduced incompatible change in reclaim resources workflow code
(extra local activity call). If new version is rolled out while previous
workflow is running, it will generate NDE. This PR adds proper version
check (patch API) to avoid it.

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

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Run upgrade locally.

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

## 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/`? -->
No.

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