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
Quarkus 2.x uses Vertx 4.x which provides Redis client which provides more features than exposed via Quarkus configuration options. It would be great to configure features like TLS or AUTH (possibly others) directly via Quarkus configuraiton properties to avoid manual configuration of Redis client used by Vertx used by Quarkus.
Functionality is already provided by existing code as discussed in #13161. This enhancement is only about configuration propagation from Quarkus to Vertx Redis client.
The text was updated successfully, but these errors were encountered:
Description
Quarkus 2.x uses Vertx 4.x which provides Redis client which provides more features than exposed via Quarkus configuration options. It would be great to configure features like TLS or AUTH (possibly others) directly via Quarkus configuraiton properties to avoid manual configuration of Redis client used by Vertx used by Quarkus.
Functionality is already provided by existing code as discussed in #13161. This enhancement is only about configuration propagation from Quarkus to Vertx Redis client.
The text was updated successfully, but these errors were encountered: