Spring Cloud Config Client-Side PropertySource Order Different between Spring Boot 2.1.x and 2.2.x

@spencergibb @ryanjbaxter

We are in the process of upgrading from Spring Boot 2.1.x (Greenwich.SR1) -> 2.2.x (Hoxton.SR1)

We are using the configuration server for externalized configuration and BOTH versions are hitting the same configuration server and the configuration being served is in the correct order.

However, if we hit the environment actuator endpoint on the client:

In this example, the application name is "build-api" and the profile is set to "local":

The 2.1.x version (which is working):

{
"activeProfiles": ["local"],
"propertySources": [
{"name": "server.ports","properties": {}},
{"name": "commandLineArgs","properties": {}},
{"name": "servletContextInitParams","properties": {}},
{"name": "systemProperties","properties": {}},
{"name": "systemEnvironment","properties": {}},
{"name": "configService:configClient","properties": {}},
{"name": "configService:https://github.com/buildcom/config.git/apps/build-api-local.yml","properties": {}},
{"name": "configService:https://github.com/buildcom/config.git/global/application-local.yml","properties": {}},
{"name": "configService:https://github.com/buildcom/config.git/apps/build-api.yml","properties": {}},
{"name": "configService:https://github.com/buildcom/config.git/global/application.yml","properties": {}},
{"name": "applicationConfig: [classpath:/application.yml]","properties": {}},
{"name": "springCloudClientHostInfo","properties": {}},
{"name": "applicationConfig: [classpath:/bootstrap.yml] (document #0)","properties": {}},
{"name": "class path resource [api-client-rest.properties]","properties": {}},
{"name": "defaultProperties","properties": {}}
]}

The 2.2.x version (it is ordering the default properties BEFORE the profile specific ones):

{
"activeProfiles": ["local"],
"propertySources": [
{"name": "server.ports","properties": {}},
{"name": "commandLineArgs","properties": {}},
{"name": "servletContextInitParams","properties": {}},
{"name": "systemProperties","properties": {}},
{"name": "systemEnvironment","properties": {}},
{"name": "bootstrapProperties-https://github.com/buildcom/config.git/global/application.yml","properties": {}},
{"name": "bootstrapProperties-https://github.com/buildcom/config.git/apps/build-api.yml","properties": {}},
{"name": "bootstrapProperties-https://github.com/buildcom/config.git/global/application-local.yml","properties": {}},
{"name": "bootstrapProperties-https://github.com/buildcom/config.git/apps/build-api-local.yml","properties": {}},
{"name": "bootstrapProperties-configClient","properties": {}},
{"name": "springCloudClientHostInfo","properties": {}},
{"name": "applicationConfig: [classpath:/application.yml]","properties": {}},
{"name": "applicationConfig: [classpath:/bootstrap.yml] (document #0)","properties": {}},
{"name": "springCloudDefaultProperties","properties": {}},
{"name": "class path resource [api-client-rest.properties]","properties": {}}
]}

Comment From: spencergibb

We just fixed something like that in commons, can you try with snapshots?

Comment From: tkvangorder

Yep, it is fixed on the snapshots build, I think this is the PR that fixed it: https://github.com/spring-cloud/spring-cloud-commons/pull/670

It looks like we will have to wait until Huxton.SR3. Thanks. I will close this.

Comment From: benhubert

I can confirm, this issue is fixed when I load dependencies from the current org.springframework.cloud:spring-cloud-dependencies:Hoxton.BUILD-SNAPSHOT (but not with Hoxton.SR2).

Would be cool to get Hoxton.SR3 released soon.

Comment From: spencergibb

The next few days