-
Notifications
You must be signed in to change notification settings - Fork 413
Closed
Labels
Description
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.