Spring Active Profiles inconsistencies

[sstarcher]

On the command line I specify --spring.active.profiles=A
at the top of /application.yml I specify spring.profiles.active: B

Environment.getActiveProfiles() returns A
But yml files that have profile B as active get loaded instead of A.

If I specify new SpringApplicationBuilder().profiles("C") in addition to the above.
Environment.getActiveProfiles() returns A,C
And C is getting loaded. Which would be my expectation.

[sstarcher]

I have narrowed in on the exact behavior I'm seeing. The above difference between --spring.active.profiles and new SpringApplicationBuilder().profiles("") was incorrect.

Using the data below as is you would expect "version" to be equal to B which is correct, but if you specify --spring.profiles.active to A you would expect "version" to be equal to A, but version is still B.

If --spring.profiles.active is C then "version" is equal to C. It seems to be taking the last value as would be expected if spring.profiles.active was set to "A,C" which would be expected, but in our case --spring.profiles.active should be fully replacing the value of spring.profiles.active in the yml.

spring.profiles.active: B
---
spring:
  profiles: A
version: A
---
spring:
  profiles: B
version: B
---
spring:
  profiles: C
version: C
---

[philwebb]

Could you try the latest snapshot? I am trying to recreate the issue without much luck.

[sstarcher]

I'll try to recreate it using a test and the latest SNAPSHOT

try using the above yml example and on the command line specify --spring.profiles.active=A and check the value of version.

[philwebb]

OK, no need to check. I have replicated the problem.

[philwebb]

@dsyer Could you review f0bfecd in case I have missed anything.

[dsyer]

Looks OK to me