Migration Guide 3.4

Vert.x HTTP

Configuration

The Vert.x HTTP configuration was migrated to the new ConfigMapping infrastructure. The main visible change is that the configuration classes are now interfaces.

If you were consuming them in an extension to get the configuration property values (for instance by injecting io.quarkus.vertx.http.runtime.HttpConfiguration), you will have to adjust your code accordingly to use the interface methods (instead of the class fields). Adding () at the end of each consumed field should be all that’s needed in most cases.

CORS

The configuration property quarkus.http.cors has been renamed to quarkus.http.cors.enabled. Both properties are valid, and quarkus.http.cors.enabled has priority between both. In the future, the old property quarkus.http.cors will be marked as deprecated.

Elasticsearch

Dev Services

The Elasticsearch Dev Services now default to starting Elasticsearch 8.9, instead of 8.8 previously.

Also, Elasticsearch Dev Services will now automatically start OpenSearch instead of Elasticsearch when they detect that a Quarkus extension expects OpenSearch. Currently only the Hibernate Search extension takes advantage of this feature.

To force the use of a specific distribution (Elasticsearch vs. OpenSearch) or version, configure the container image explicitly.