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

Wrong priority order of multiple configs in bootstrap mode #302

Closed
woshikid opened this issue Oct 10, 2022 · 2 comments
Closed

Wrong priority order of multiple configs in bootstrap mode #302

woshikid opened this issue Oct 10, 2022 · 2 comments

Comments

@woshikid
Copy link

woshikid commented Oct 10, 2022

When using Spring Cloud Config, the priority order of multiple configs is as follow: (both import mode and bootstrap mode)

1. configserver:foo-dev.yml
2. configserver:application-dev.yml
3. configserver:foo.yml
4. configserver:application.yml

and Spring Cloud Zookeeper Config take a similar order when using spring.config.import

1. zookeeper:config/foo,dev
2. zookeeper:config/application,dev
3. zookeeper:config/foo
4. zookeeper:config/application

BUT when using bootstrap mode, the client load configs in a strange priority order:

1. zookeeper:config/foo,dev
2. zookeeper:config/foo
3. zookeeper:config/application,dev
4. zookeeper:config/application

this can be confirmed by using /actuator/env api.

@woshikid
Copy link
Author

I've made a PR #303 on this.

@spencergibb
Copy link
Member

Closing in favor of #303

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants