We have upgraded from sprig version 2.1.x to 2.4.X and cloud - Greenwich to 2020.0.X. Included spring boot spring-cloud-starter-bootstrap to load properties.. its working fine on app initial startup. However actuator/refresh isn't working... Upon debugging further found out that - Its not taking name from spring.application.name while connecting to cloud config server - application name defaulted to 'application'
Reference - https://github.com/spring-cloud/spring-cloud-config/blob/63e0a99f898fe28bf09bb1e1d5f88be19dd01d0f/spring-cloud-config-client/src/main/java/org/springframework/cloud/config/client/ConfigServicePropertySourceLocator.java#L214
Comment From: ryanjbaxter
It is only not working when you make a POST to /actuator/refresh?
Comment From: shivudu
Yes, on startup it’s loading properties, but when I do POST actuator/refresh it’s not working.
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: dyroberts
@ryanjbaxter I'm experiencing this with spring-cloud-services acceptance tests as well. Basic config-client app is exposing it. I'm not using the legacy starter though.
Comment From: dyroberts
Here's the apps (client/server) I used to reproduce locally: https://github.com/dyroberts/1803-spring-cloud-config Using the default host and port (localhost:8888) works. Anything else seems not to work.
Comment From: spencergibb
ping @dyroberts I'm unable to reproduce using your sample. What exact steps do I need to do to replicate?
Comment From: shivudu
Hi @spencergibb , just have cloud config-client with version 2020.0.1 and add dependency spring-cloud-starter-bootstrap, use legecy loading using property - spring.cloud.config.uri to pull props from server. do a post on actuator/refresh.
Then if you can debug this method upon refresh, you can notice name (spring.application.name) defaulted to 'application'. https://github.com/spring-cloud/spring-cloud-config/blob/63e0a99f898fe28bf09bb1e1d5f88be19dd01d0f/spring-cloud-config-client/src/main/java/org/springframework/cloud/config/client/ConfigServicePropertySourceLocator.java#L214
Comment From: shivudu
@dyroberts if you are using spring.cloud.config.uri with cloud version 2020.0.1 you should have dependency / use properties to get it working on initial startup of application. check out - https://spring.io/blog/2020/12/22/spring-cloud-2020-0-0-aka-ilford-is-available Also note - spring.cloud.config.uri should be in env /bootstrap.properties to get it working
Comment From: dyroberts
Here's the apps (client/server) I used to reproduce locally: https://github.com/dyroberts/1803-spring-cloud-config Using the default host and port (localhost:8888) works. Anything else seems not to work.
This is not reproducing the issue after all. Please disregard. I'll potentially file a separate issue if needed.
Comment From: spencergibb
@shivudu I'm unable to reproduce this problem. I'm going to need a sample as requested https://github.com/spring-cloud/spring-cloud-config/issues/1803#issuecomment-782352216
Comment From: spring-cloud-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-cloud-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.