The /actuatorendpoint goes under the /release resource. Following the precedent for api/release/logs, the functionality is similarly out of the release domain, but gets info provided by deployed app instances whose metadata are exposed via a release. Exposed via ReleaseController, this adds an ActuatorService which also depends on ReleaseService, and config for the ActuatorService. I have manually verified end-to-end functionality against the local deployer, with time | log deployed with 2 log instances.
resolves #1024
The
/actuator
endpoint goes under the/release
resource. Following the precedent forapi/release/logs
, the functionality is similarly out of the release domain, but gets info provided by deployed app instances whose metadata are exposed via a release. Exposed viaReleaseController
, this adds anActuatorService
which also depends onReleaseService
, and config for the ActuatorService. I have manually verified end-to-end functionality against the local deployer, withtime | log
deployed with 2 log instances.Depends on https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry/pull/385, https://github.com/spring-cloud/spring-cloud-deployer-kubernetes/pull/478, and https://github.com/spring-cloud/spring-cloud-deployer-local/pull/212