fix(ui): improve account deletion flow in all instances #5335
+196
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the user account deletion flow to provide clearer instructions and restrictions, especially for Community and Enterprise deployments. It introduces a warning dialog for users on these editions, disables account deletion if the user owns namespaces, and adds tests to ensure the new dialogs work as expected.
UserDeleteWarning
dialog that informs users on Community editions that accounts must be deleted via CLI, and on Enterprise editions that deletion must be performed via the Admin Console. This dialog is shown instead of the regular deletion dialog when the user is not in a Cloud instance.UserDelete
dialog to prevent account deletion if the user has owned namespaces, displaying a warning and disabling the confirm button in that case. The dialog now dynamically changes its description and error handling based on the user's namespace ownership.UserDeleteWarning.spec.ts
to verify that the correct instructions and CLI command are shown for Community and Enterprise editions.