-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide new API to programmatically create REST Client reactive #32857
Conversation
We'll need a resolution on #32856 (comment) before moving this forward |
🙈 The PR is closed and the preview is expired. |
...reactive/runtime/src/main/java/io/quarkus/rest/client/reactive/QuarkusRestClientBuilder.java
Outdated
Show resolved
Hide resolved
* @return the current builder with the connect timeout set. | ||
* @throws IllegalArgumentException if the value of timeout is negative. | ||
*/ | ||
QuarkusRestClientBuilder readTimeout(long timeout, TimeUnit unit); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably also have tests where these properties override the configured values in application.properties
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is covered by RestClientCDIDelegateBuilderTest
This comment has been minimized.
This comment has been minimized.
The new API includes these additional options: - verifyHost - trustStore by truststore and password (it was requested in quarkusio#31891) - proxyUser - proxyPassword - nonProxyHosts Fix quarkusio#32856
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
The new API includes these additional options:
Note that for the new API, I didn't add any breaking change, so users can keep using the Microprofile one.
Fix #32856