Feature: Extend support of Spring Cloud endpoints

[cdprete]

Hello.

According to the docs, only the /restart endpoint is supported from https://docs.spring.io/spring-cloud-commons/reference/spring-cloud-commons/application-context-services.html#endpoints.

It would be great if the others could be supported as well, especially /refresh and /env.

[andreasfritz]

Do you have any specific use cases where these endpoints would be helpful to you?

[cdprete]

I would like to restart/refresh applications if needed without having to go to the box and do it by hand.

[andreasfritz]

“Restart” is a useful endpoint and has therefore already been implemented.
What is a use case for performing only a refresh rather than a full restart?
(The refresh would require an additional button in the UI that would need to be visually distinct from the “Restart” button.)

[cdprete]

Restart will kill the process and, therefore, create an incident/alert/disruption in production.
If we can just refresh the context without killing the process is would be helpful.

[SteKoe]

Both actuator endpoints are already implemented as far as I see. POSTing to /actuator/env as well as /actuator/refresh is possible via the details of an instance. On the left menu, navigate to "Environment" and see the buttons "Refresh context" as well asl "Update" in "Environment Manager".

[cdprete]

So it's just the documentation missing them?

@SteKoe the confusing part is to understand what's really supported/implemented.
For example, for refresh, the docs mentions and links to /gateway/refresh which is proper only to Spring Cloud Gateway and it's different from the one in https://docs.spring.io/spring-cloud-commons/reference/spring-cloud-commons/application-context-services.html#endpoints.
For env, the Spring Boot docs don't mention it's editable (no POST or PUT defined, but only GET), while the one in the link above is.