-
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
2.15.0 backports 2 #29713
Merged
Merged
2.15.0 backports 2 #29713
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closes quarkusio#10673 (cherry picked from commit dc5f031)
(cherry picked from commit 92bd8d8)
(cherry picked from commit 564d112)
(cherry picked from commit 0785582)
Closes: quarkusio#29617 (cherry picked from commit 06b13d5)
Before these changes, we only can disable the hostname verification in Rest Client classic by providing the following property: ``` quarkus.rest-client.extensions-api.hostname-verifier=io.quarkus.restclient.NoopHostnameVerifier ``` However, this is not working in Rest Client reactive because setting a hostname verifier strategy is not supported by the Vert-x HTTP Client. With these changes, we have added a new property in both Rest Client classic and reactive `quarkus.rest-client.extensions-api.verify-host=true or false`. In Rest Client classic, when disabling the verify host, internally it will add the `NoopHostnameVerifier` strategy. In Rest Client reactive, it will properly configure the Vert.x HTTP client to disable the hostname verification. Therefore, in both Rest Client implementations (classic and reactive), the behaviour is the same. Fix quarkusio#27901 (cherry picked from commit 941d3a6)
(cherry picked from commit ddc481f)
(cherry picked from commit 2f9ff6f)
This adds further details about the fix and the discussion in quarkusio#29562. It clearifies that alias is also fine instead of podman-docker, just redirects the user to podman for install instructions ( they change over time, and more linux variant are shown there, no need duplicate and maintain), and finally, it shows a way of running podman as service without systemd (relevant on wsl up until recently for example, and users a most likely stuck with slightly older wsl's in a few places). Signed-off-by: Josef Andersson <josef.andersson@gmail.com> (cherry picked from commit 9e85d7e)
(cherry picked from commit 71c6f7d)
Closes: quarkusio#29043 (cherry picked from commit 17eecf2)
…uration parameter (cherry picked from commit d1dfafa)
This annotation allows to actually turn a String into a List<String> automatically for each query param value Resolves: quarkusio#29528 (cherry picked from commit f695369)
Fix quarkusio#29497 (cherry picked from commit e673ea5)
Fixes quarkusio#28372 (cherry picked from commit e8b82f6)
(cherry picked from commit 6cb6ae7)
(cherry picked from commit 102d15e)
(cherry picked from commit 811b283)
Per Andy's request. (cherry picked from commit f670cfc)
- this is index is mandatory and is used to discover beans - the computing index is optional and can be used for other tasks, e.g. during type-safe resolution - if the computing index is not present the immutable index is used instead - fixes quarkusio#29575 (cherry picked from commit c2ab342)
(cherry picked from commit 1c16ec1)
(cherry picked from commit 2c3865c)
(cherry picked from commit 9f7ee4e)
(cherry picked from commit b3edfef)
(cherry picked from commit bd521fc)
According to https://github.com/servicebinding/spec#workload-projection, `uri` is part of the standard (cherry picked from commit c205494)
- make sure that an interface method of an interface-based client proxy is invoked upon the provider type and not the type that declares the method - fixes quarkusio#29593 (cherry picked from commit 4d51083)
quarkus-bot
bot
added
area/arc
Issue related to ARC (dependency injection)
area/cli
Related to quarkus cli (not maven/gradle/etc.)
area/dependencies
Pull requests that update a dependency file
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
area/documentation
area/hibernate-orm
Hibernate ORM
area/hibernate-reactive
Hibernate Reactive
area/jbang
Issues related to when using jbang.dev with Quarkus
area/keycloak
area/kubernetes
area/maven
area/panache
area/persistence
OBSOLETE, DO NOT USE
area/platform
Issues related to definition and interaction with Quarkus Platform
area/rest
area/spring
Issues relating to the Spring integration
area/tracing
area/vertx
labels
Dec 6, 2022
Failing Jobs - Building 15c75c5
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/arc
Issue related to ARC (dependency injection)
area/cli
Related to quarkus cli (not maven/gradle/etc.)
area/dependencies
Pull requests that update a dependency file
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
area/documentation
area/hibernate-orm
Hibernate ORM
area/hibernate-reactive
Hibernate Reactive
area/infra
internal and infrastructure related issues
area/jbang
Issues related to when using jbang.dev with Quarkus
area/keycloak
area/kubernetes
area/maven
area/panache
area/persistence
OBSOLETE, DO NOT USE
area/platform
Issues related to definition and interaction with Quarkus Platform
area/rest
area/spring
Issues relating to the Spring integration
area/tracing
area/vertx
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please don't merge, I will merge it myself.