Different profile precedence introduced in Spring Boot 2.0.2 - include profile now comes after active.

[davidmelia]

Hi,

Spring Boot 2.0.2 has introduced a different profile precedence when compared to previous versions.

It's very easy to reproduce.

1. In STS create a Spring boot starter web project
2. In the application.properties add spring.profiles.include=include
3. Build and run the project with java -jar ./target/somename-0.0.1-SNAPSHOT.jar --spring.profiles.active=active
4. You will see The following profiles are active: active,include which is incorrect

Downgrade the pom to Spring boot 2.0.1 and run again and you will see
The following profiles are active: include,active
which is correct

Spring boot 1.5.13 also gives The following profiles are active: include,active

I'm using Java 8 & MacOS High Sierra.

Thanks

[wilkinsona]

See #11380, part of which corrected the ordering of the logged profiles to accurately reflect the order in which they were processed.

You will see The following profiles are active: active,include which is incorrect

Can you please explain why you consider this to be incorrect?

spring.profiles.active is a command line argument so it’s seen first and active is made active. application.properties is then read at which point include is made active. Given this ordering active,include would seem to be correct.

[davidmelia]

Hi,

If I explain my use case:

I'm deploying in a microservice architecture so I've created a common microservices maven dependency containing spring boot properties I want across all Microservices:
application-microservice.properties
and also contains a common override when I deploy to the cloud
application-cloud.properties

Every microservice pulls in this maven dependency & switches on the first profile via
spring.profiles.include=microservice
in the local application.properties of that service.

When I deploy to the cloud I additionally add the command line argument
--spring.profiles.active=cloud
which turns on the override.

What's happening now is the cloud profile property is being overridden by the microservice profile and therefore Spring Boot 2.0.2 is quite a large breaking change for me.

To illustrate this further if I have a spring boot app with the following properties

application-cloud.properties
    some.key=cloudprop
application-microservice.properties
    some.key=microserviceprop
application.properties
    spring.profiles.include=microservice

and a command line active profile of 'cloud' then Spring Boot <=2.0.1 outputs 'cloudprop' where as 2.0.2 outputs 'microserviceprop'

Thanks

[wilkinsona]

That additional description is very useful. Thank you.

[jpopadak]

I seem to be having the exact same issues. Anything in include is overriding my active profile.