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
ContainerDiscovery uses the WebClient to talk to the Docker or Podman APIs. This may not make sense to port to QuarkusRestClient since this requires a Unix domain socket and Netty native transport.
Health uses the WebClient to test other services' health (datasource, dashboard, reports). This looks like it can also be converted easily, and cleanly with @Url.
Once this is done, hostname verification (and other TLS configuration properties) can be controlled for each particular client, so checks can be disabled only where specifically needed.
The text was updated successfully, but these errors were encountered:
Describe the feature
The Mutiny/Vertx WebClient should be replaced by QuarkusRestClient where possible:
https://quarkus.io/guides/rest-client
This provides more configuration options and nice things like service interfaces rather than dealing with direct HTTP responses.
jfr-datasource
. This should be pretty easy to convert to a QuarkusRestClient similar to the ReportSidecarService.@Url
annotation in Quarkus 3.16+ it should also be pretty easy to convert this.@Url
.Anything other information?
See:
Once this is done, hostname verification (and other TLS configuration properties) can be controlled for each particular client, so checks can be disabled only where specifically needed.
The text was updated successfully, but these errors were encountered: