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.

Sign up for GitHub

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

Jump to bottom

当命名空间不存在时，仍然可以创建配置。When the namespace does not exist, a configuration can still be created. #12889

Open
fuhouyu opened this issue Nov 23, 2024 · 3 comments · May be fixed by #12890
Open

当命名空间不存在时，仍然可以创建配置。When the namespace does not exist, a configuration can still be created. #12889

fuhouyu opened this issue Nov 23, 2024 · 3 comments · May be fixed by #12890
Assignees
@shiyiyue1102
Labels
area/Nacos Core kind/discussion Category issues related to discussion

Comments

@fuhouyu
Copy link
Contributor

fuhouyu commented Nov 23, 2024

Issue Description

命名空间不存在或已经被删除时，仍然可以创建配置。在创建完成再回到页面，命名空间在页面上会存在找不到的问题
When the namespace does not exist or has been deleted, a configuration can still be created. After the creation is completed and you return to the page, there will be an issue of the namespace existing but not being found.

image

Describe what happened (or what feature you want)

Describe what you expected to happen

不允许访问不存在的命名空间，及创建配置
Access to non-existent namespaces is not allowed, as well as creating configurations.

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?
@fuhouyu
Copy link
Contributor Author

fuhouyu commented Nov 23, 2024

@i will solve it@

@fuhouyu fuhouyu linked a pull request Nov 23, 2024 that will close this issue
Open
5 tasks
@shiyiyue1102 shiyiyue1102 self-assigned this Nov 26, 2024
@KomachiSion KomachiSion added area/Nacos Core kind/discussion Category issues related to discussion labels Nov 27, 2024
fuhouyu added a commit to fuhouyu/nacos that referenced this issue Nov 30, 2024
@fuhouyu
fix: alibaba#12889 ,when namespace is not exists,then throw error
2678342
@KomachiSion
Copy link
Collaborator

I suggest you build an proposal in issue discussion first. And I suggest make it into 3.0 version. Because this will intercept more usage in old version.

@fuhouyu
Copy link
Contributor Author

fuhouyu commented Dec 3, 2024

我建议你先在问题讨论中建立一个提案。我建议把它做成 3.0 版本。因为这会拦截旧版本中的更多使用。

好的老师。那我是否应该撤销当前的PR，在需要的时候，在3.0的版本中再进行添加吗？

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shiyiyue1102 shiyiyue1102

Labels
area/Nacos Core kind/discussion Category issues related to discussion
Projects
None yet
Milestone
No milestone
3 participants
@shiyiyue1102 @KomachiSion @fuhouyu