New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail hard if spring.profiles.include is used with new config processing #22693
Comments
We currently still support |
+1 to @mbhave
Where application-security.properties
application.properties
application-local_*.properties and every major profile such as prod, stage etc has at top spring.profiles.include=common,common_pg,security
# ... In a new project everything was working on local but suddenly blasted on staging. I was unable to figure out the problem until I started debugging the spring boot source code. There I found |
Thanks for sharing your experience, @perilbrain. We started failing hard in 2.4.0.M2 (this issue) but this was then relaxed in 2.4.0.M3 to allow |
Hi there, I've just come across this exact issue as the other user (only seeing this when pushing to stage!) when updating from a much older version of Spring Boot. Am I right in thinking that in 99% of cases, updating to I'm pretty new to Spring Boot configuration/updates so just want to check that I'm on the right track, and also leave a trail for any other noob devs who come across this thread. |
@AJMcDee It's hard to offer specific advice without more details, but generally speaking the |
spring.profiles.include
andspring.profiles
are not used by the new config data code. However, they are still valid if legacy processing is switched on. We should consider if we want to deprecate them in the metadata.We also need to update the documentation which mentions
spring.profiles.include
here.The text was updated successfully, but these errors were encountered: