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

nacos导入配置文件无法覆盖原有的配置文件 #5934

Closed
RonaldFletcher opened this issue Jun 3, 2021 · 1 comment · Fixed by #6017
Closed

nacos导入配置文件无法覆盖原有的配置文件 #5934

RonaldFletcher opened this issue Jun 3, 2021 · 1 comment · Fixed by #6017
Assignees
Labels
area/Config kind/bug Category issues or prs related to bug.

Comments

@RonaldFletcher
Copy link

Describe the bug
A clear and concise description of what the bug is.
我使用nacos导入配置文件的时候无法覆盖原有的配置
image
image
导入之后原有dateid的配置没有被覆盖
导入的压缩文件如下
image
image

nacos版本1.4.1 内嵌数据库集群部署

Expected behavior
A clear and concise description of what you expected to happen.

Acutally behavior
A clear and concise description of what you actually to happen.

How to Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Desktop (please complete the following information):

  • OS: [e.g. Centos]
  • Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
  • Module [e.g. naming/config]
  • SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]

Additional context
Add any other context about the problem here.

@KeRan213539
Copy link
Collaborator

KeRan213539 commented Jun 8, 2021

确认该问题存在, 1.4.2 , 2.0.1 也存在该问题, 我们会尽快修复

@KeRan213539 KeRan213539 mentioned this issue Jun 8, 2021
5 tasks
KeRan213539 added a commit to KeRan213539/nacos that referenced this issue Jun 9, 2021
@KeRan213539 KeRan213539 mentioned this issue Jun 9, 2021
5 tasks
KomachiSion pushed a commit that referenced this issue Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/Config kind/bug Category issues or prs related to bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants