Ryan Baxter
Ryan Baxter
There are some suggested workaround here https://github.com/spring-cloud/spring-cloud-gateway/issues/1514
@joshrosso that makes sense, can you create a PR for the 1.1.x branch?
Awesome thanks!
It is used internally, that is how we push the image to dockerhub
No they must match at the moment but this is a reasonable enhancement
That endpoint has existed and continues to exist for a long while now, you might need to enable it and expose it
When I go to `http://localhost:8080/actuator` I see the refresh endpoint using your example ``` { "_links": { "self": { "href": "http://localhost:8080/actuator", "templated": false }, "refresh": { "href": "http://localhost:8080/actuator/refresh", "templated": false...
That's why we suggest you use the Spring Cloud Bom and let it manage the dependencies for you. The refresh endpoint is part of Spring Cloud Commons not Sprint Cloud...
Not sure. Any help would be appreciated though, the team is very busy.
Can you provide a [complete, minimal, verifiable sample](https://stackoverflow.com/help/mcve) that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip...