Closed woshikid closed 1 year ago
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
I've made a PR #303 on this.
Closing in favor of #303
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.