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 #798

Open
woshikid opened this issue Oct 10, 2022 · 0 comments
Open

Wrong priority order of multiple configs in bootstrap mode #798

woshikid opened this issue Oct 10, 2022 · 0 comments

Comments

@woshikid
Copy link

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 Consul Config take a similar order when using spring.config.import

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

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

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

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

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

2 participants