-
Notifications
You must be signed in to change notification settings - Fork 104
Add java-cfenv reconfiguration jar #76
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
Conversation
dyroberts
commented
Feb 13, 2020
•
edited
Loading
edited
- Classic reconfiguration jar remains in its own module
- New reconfiguration jar...
- uses java-cfenv to set cloud profile and property source
- this initial implementation only adds vcap_application properties in 'cloud' property source, not vcap_services, and does not maintain connectors' property naming convention
- drops bean replacement functionality
- instead leverages java-cfenv-boot for assorted auto-configuration of bound services
- had to add the java-cfenv-boot's spring.factories entries to the spring.factories file in this new jar
|
72f6e13
to
3fd2bb8
Compare
- Classic reconfiguration jar remains in its own module - New reconfiguration jar... - uses java-cfenv to set cloud profile and property source - this initial implementation only adds vcap_application properties in 'cloud' property source, not vcap_services, and does not maintain connectors' property naming convention - drops bean replacement functionality - instead leverages java-cfenv-boot for assorted auto-configuration of bound services - had to add the java-cfenv-boot's spring.factories entries to the spring.factories file in this new jar
3fd2bb8
to
0963a23
Compare
Regarding the lack of a fully populated 'cloud' property source, java-cfenv basic usage has this case covered using SpEL. https://github.com/pivotal-cf/java-cfenv#use-with-spring |
It would be nice to have a cleaner solution to the |
The |
Why would this file need to change with JBP auto-reconfiguration has always supported an intentionally limited set of connection types, so it wouldn't need to change when new connection types are added to |
Thanks @scottfrederick! I was thinking the same about the cloud property source. Regarding spring.factories file, I just meant that there's the possibility that some java-cfenv version in the future might require an update here. Glad to hear you're ok with this approach. |
@nebhale Any idea when you might have a chance to look at this? :) |
Cross-posting here for awareness: cloudfoundry/java-buildpack#779 (comment) |
Closing as we have decided to deprecate & remove auto-configuration versus trying to move forward with it. |