ostara
ostara copied to clipboard
Ability to handle different exposure levels of actuator endpoints
Actuator endpoints can reveal more or less information depending on configuration. We need to be able to detect this and display things accordingly. /health example when exposed: {"status":"UP","components":{"db":{"status":"UP","details":{"database":"MySQL","validationQuery":"isValid()"}},"discoveryComposite":{"description":"Discovery Client not initialized","status":"UNKNOWN","components":{"discoveryClient":{"description":"Discovery Client not initialized","status":"UNKNOWN"}}},"diskSpace":{"status":"UP","details":{"total":133003395072,"free":27105759232,"threshold":10485760,"exists":true}},"livenessState":{"status":"UP"},"ping":{"status":"UP"},"rabbit":{"status":"UP","details":{"version":"3.11.2"}},"readinessState":{"status":"UP"},"refreshScope":{"status":"UP"}},"groups":["liveness","readiness"]}
When not exposed: {"status":"UP"}
Additionally some endpoints may be deliberately hidden, so all features should be toggle able based on what we can see
Partial implementation