You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SE: The HealthSupport type is replaced by the combination of ObserveFeature and HealthObserver. See the doc for details.
SE: The default health endpoint is now at /observe/health instead of /health as in 3.x.
SE: SE applications now use the io.helidon.health.HealthCheck and ...HealthCheckResponse types instead of the counterpart types from MicroProfile Health.
SE: Adding the helidon-health and helidon-health-checks dependencies to a project automatically adds the built-in health checks and the health endpoint to the application; application code no longer needs to explicitly add health to the application unless it also disables WebServer.Builder.featuresDiscoverServices.
Summarize actions customers must take to migrate code
OK to reference external specs or documents (for example MicroProfile specs)
The text was updated successfully, but these errors were encountered:
Problem Description
We need to update docs for 4.x
Guidelines
Migration Impact
Summarize incompatibilities between Helidon 3 and Helidon 4.
health.endpoint
config key instead ofhealth.web-context
.features.observe.observers.health.endpoint
key instead ofhealth.web-context
.endpoint
method on theHealthObserver.Builder
type instead of thewebContext
method on theHealthSupport.Builder
type.server.features.observe.socket
config key:HealthSupport
type is replaced by the combination ofObserveFeature
andHealthObserver
. See the doc for details./observe/health
instead of/health
as in 3.x.io.helidon.health.HealthCheck
and...HealthCheckResponse
types instead of the counterpart types from MicroProfile Health.helidon-health
andhelidon-health-checks
dependencies to a project automatically adds the built-in health checks and the health endpoint to the application; application code no longer needs to explicitly add health to the application unless it also disablesWebServer.Builder.featuresDiscoverServices
.Summarize actions customers must take to migrate code
OK to reference external specs or documents (for example MicroProfile specs)
The text was updated successfully, but these errors were encountered: