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.
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
Allow users to delete AppNamespace #4499
Allow users to delete AppNamespace #4499
Changes from 52 commits
fe75b4d
99bf97a
1579f41
9f65eed
d7d3fd9
7329fab
5def448
6942564
0fc1f91
61ad016
587ce33
9de6563
9aab632
050dd0a
5a64035
0648fbd
35bd3a6
bc8149b
e771bdd
9a1ad83
3efef37
1274281
a968932
df8942c
f98175a
710cdd6
3c162b6
0101a3f
cc6f568
21dd30c
c1eeb41
e85d645
8b0056d
347e07b
d8eb437
19bae52
7e40fa1
fbbb02d
19cee24
91ba3b7
94ad542
64e1b0b
36ce5e2
c1364c2
76ed2ea
db8cf3d
3e4616d
47297cc
1c320e7
e723db5
df1dc49
ef6325d
f4c6881
fae7f9f
1be9790
9dcc111
d388f0e
66ee7d6
ecd91bc
197b684
b0a5f45
4ec7117
19d8940
2c942f4
454488d
6c57b80
cb14888
4696f13
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
For public and private namespaces, I think we still need to check the instances by
checkMasterInstance
andcheckBranchInstance
?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.
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.
In this case, there is a detailed message indicating that this operation will cause the instances unable to get the configuration, so I think it's ok to not
checkMasterInstance
andcheckBranchInstance
.If we don't check for public and private namespaces, I suppose we don't need to check for linked namespaces?
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.
Yes, I think they are the same type of problem
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.
So maybe we could simplify the logic as the following?
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.
The logic for deleting different types of Namespace on the user side has been unified, and a uniform instance usage prompt message is added before deletion, e.g.