-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
ConfigData imports cannot override profile specific imports #25766
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Mar 23, 2021
philwebb
changed the title
Spring boot 2.4.2 reverses the property order precedence if spring.config.import is supplied via application.yml
ConfigData imports cannot override profile specific imports
Apr 5, 2021
philwebb
added
type: bug
A general bug
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Apr 5, 2021
Thanks for reporting the issue, this particular use-case was overlooked when we designed the new |
philwebb
added a commit
that referenced
this issue
Apr 6, 2021
Thank you @philwebb for taking care of this. |
philwebb
added a commit
that referenced
this issue
Apr 8, 2021
Add convenience methods to ConfigData.Options to allow new Options instances to be created with options excluded or included. See gh-25766
This was referenced Apr 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Lets say there is a profile
baz
.classpath:application-baz
(local to jar) is overridingapplication-baz
from spring cloud config repository, which is incorrect.i.e., values from jar local property source gets precedence over the spring cloud config repo's property source.
Test case illustrating the issue:
spring-cloud/spring-cloud-config#1839 --> This PR has the test case in it .
See open issue on spring cloud board:
spring-cloud/spring-cloud-config#1838
Spring cloud has suggested the bug to be logged under spring boot.
The workaround we have been applying is
spring.config.import
from application'ssrc/main/resources/application.yml
spring.config.import
asJAVA_OPTS
when starting the service.The text was updated successfully, but these errors were encountered: