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

Delete Namespace: fix validation of replicated namespace #7069

Merged

Conversation

alexshtin
Copy link
Member

@alexshtin alexshtin commented Jan 10, 2025

What changed?

Delete Namespace: fix validation of replicated namespace.

Why?

Namespace should be deletable when:

  1. It is active in the current cluster (even if replicated),
  2. Doesn't belong to current cluster (current cluster was removed from cluster list).

How did you test it?

Added new tests, existing tests, manual run.

Potential risks

No risks.

Documentation

No.

Is hotfix candidate?

No.

@alexshtin alexshtin requested a review from a team as a code owner January 10, 2025 20:30
@alexshtin alexshtin requested a review from yux0 January 10, 2025 20:35
@alexshtin alexshtin force-pushed the fix/delete-ns-replication-validation branch from ae508e9 to 8e11655 Compare January 10, 2025 20:39
@alexshtin alexshtin merged commit 35f9654 into temporalio:main Jan 10, 2025
49 checks passed
@alexshtin alexshtin deleted the fix/delete-ns-replication-validation branch January 10, 2025 22:16
bergundy pushed a commit that referenced this pull request Jan 10, 2025
## What changed?
<!-- Describe what has changed in this PR -->
Delete Namespace: fix validation of replicated namespace.

## Why?
<!-- Tell your future self why have you made these changes -->
Namespace should be deletable when:
1. It is active in the current cluster (even if replicated),
2. Doesn't belong to current cluster (current cluster was removed from
cluster list).

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Added new tests, existing tests, manual run.

## 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) -->
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.

2 participants