-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[pulsar-broker] Added support to force deleting tenant #8103
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
Conversation
I've fixed the |
// Check deleting non-existing property | ||
try { | ||
properties.deleteTenant("non-existing"); | ||
properties.deleteTenant(response, "non-existing", false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the test related to this change? I think the test should cover there are namespaces and topics under a tenant, then we delete the tenant forcefully should success.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change adds a force option so the test need pass this option. I can add a test to cover the above situations later.
move to 2.8.0 first |
@codelipenghui I can add a test to cover your comments and we expect this feature as soon as possilbe. Can this be introduced in coming 2.7.0? |
@codelipenghui @jiazhai I have added a test, please help to take a review when available, thanks. |
/pulsarbot run-failure-checks |
Close this and submit a new pull request using metadata-api. |
Motivation
Some users expect an option to force deleting tenant for simplicity, it can be useful in some situations.
Modifications
Add a optional field to force the deletion of all stuffs related to tenant.