We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
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.
/actuator/env
The text was updated successfully, but these errors were encountered:
I've made a PR #303 on this.
Sorry, something went wrong.
Closing in favor of #303
No branches or pull requests
When using Spring Cloud Config, the priority order of multiple configs is as follow: (both import mode and bootstrap mode)
and Spring Cloud Zookeeper Config take a similar order when using
spring.config.import
BUT when using bootstrap mode, the client load configs in a strange priority order:
this can be confirmed by using
/actuator/env
api.The text was updated successfully, but these errors were encountered: