Describe the bug After upgrading from spring-cloud-dependencies 2021.0.7 to 2021.0.8 we notice that the active profiles are no longer as expected. These services are on Spring Boot 2.17.4 btw.
The bootstrap.yml specifies: dev,local-vault The command-line specifies: production
In the past our pod would be started with just the production profile. Since release 2021.0.8 it is started with all 3 profiles.
Comment From: ryanjbaxter
Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file.
Comment From: robsmorenburg
I tried, but was not able to have a failing minimal service.
Comment From: ryanjbaxter
If you can't provide a sample it will be hard for us to help
Comment From: robsmorenburg
I understand
Comment From: leovx
Describe the bug After upgrading from spring-cloud-dependencies 2021.0.7 to 2021.0.8 we notice that the active profiles are no longer as expected. These services are on Spring Boot 2.17.4 btw.
The bootstrap.yml specifies: dev,local-vault The command-line specifies: production
In the past our pod would be started with just the production profile. Since release 2021.0.8 it is started with all 3 profiles.
Hi @robsmorenburg, I think you are talking about this issue https://github.com/spring-cloud/spring-cloud-commons/issues/1285, no worries, we have fixed it in the next version (2021.0.9).