Used for DDL generation and also for the SQL import scripts.

Setting it to true is obviously not recommended in production.

• DISABLED means no login will be attempted
• NONE means a login will be attempted if the server supports in and login credentials are set
• REQUIRED means that a login will be attempted if the server supports it and the send operation will fail otherwise
• XOAUTH2 means that a login will be attempted using Google Gmail Oauth2 tokens

Disabled by default on PROD, enabled by default on DEV and TEST modes.

• request-response - enables logging request and responses, including redirect responses
• all - enables logging requests and responses and lower-level logging
• none - no additional logging

If this is set to warn the application will warn at start up.

If this is set to fail the application will fail at start up.

Native tests leveraging@io.quarkus.test.junit.TestProfile are always run with quarkus.configuration.build-time-mismatch-at-runtime = fail.

By default, the health check includes all configured data sources (if it is enabled).

This is a global setting and is not specific to a datasource.

Set to 0 to disable background validation.

When enabling XA you will need a driver implementing javax.sql.XADataSource.

This is a global setting and is not specific to a datasource.

NOTE: This is different from the "jdbc.enable-metrics" property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.

The locale must be specified in the IETF BCP 47 format e.g. en-US or fr-FR.

For instance, the Hibernate Validator extension makes use of it.

Native-image build uses this property to derive user.language and user.country for the application's runtime.

See Section 4.5.5 of the JSR 380 specification, specifically

"One must not mark a method return value for cascaded validation more than once in a line of a class hierarchy.
In other words, overriding methods on sub types (be it sub classes/interfaces or interface implementations)
cannot mark the return value for cascaded validation if the return value has already been marked on the
overridden method of the super type or interface."

See Section 4.5.5 of the JSR 380 specification, specifically

"In sub types (be it sub classes/interfaces or interface implementations), no parameter constraints may
be declared on overridden or implemented methods, nor may parameters be marked for cascaded validation.
This would pose a strengthening of preconditions to be fulfilled by the caller."

See Section 4.5.5 of the JSR 380 specification, specifically

"If a sub type overrides/implements a method originally defined in several parallel types of the hierarchy
(e.g. two interfaces not extending each other, or a class and an interface not implemented by said class),
no parameter constraints may be declared for that method at all nor parameters be marked for cascaded validation.
This again is to avoid an unexpected strengthening of preconditions to be fulfilled by the caller."

If this is the string `common`, `combined` or `long` then this will use one of the specified named formats:

- common: `%h %l %u %t "%r" %s %b`
- combined: `%h %l %u %t "%r" %s %b "%{i,Referer}" "%{i,User-Agent}"`
- long: `%r\n%{ALL_REQUEST_HEADERS}`

Otherwise, consult the Quarkus documentation for the full list of variables that can be used.

If true the uploaded files stored in quarkus.http.body-handler.uploads-directory will be removed after handling the request. Otherwise, the files will be left there forever.

If true, they will be stored in quarkus.http.body-handler.uploads-directory and will be made available via io.vertx.ext.web.RoutingContext.fileUploads(). Otherwise, the files sent using multipart/form-data will not be stored locally, and io.vertx.ext.web.RoutingContext.fileUploads() will always return an empty collection. Note that even with this option being set to false, the multipart/form-data requests will be accepted.

If true, the form attributes will be added to the request parameters; otherwise the form parameters will not be added to the request parameters

If true the body buffer is pre-allocated according to the size read from the Content-Length header. Otherwise, the body buffer is pre-allocated to 1KB, and is resized dynamically

Either an absolute path or a path relative to the current directory of the application process.

* Relative path (Default, `q`) ->
Non-application endpoints will be served from
`${quarkus.http.root-path}/${quarkus.http.non-application-root-path}`.
* Absolute path (`/q`) ->
Non-application endpoints will be served from the specified path.
* `${quarkus.http.root-path}` -> Setting this path to the same value as HTTP root path disables
this root path. All extension-provided endpoints will be served from `${quarkus.http.root-path}`.

You can still override it locally with @JsonIgnoreProperties(ignoreUnknown = false).

The locales must be specified in the IETF BCP 47 format e.g. en-US or fr-FR.

For instance, the Hibernate Validator extension makes use of it.

Native-image build uses it to define additional locales that are supposed to be available at runtime.

You need to either set a max-file-size or configure a file-suffix for it to work.

JBoss Logging supports Apache style log levels:

* org.jboss.logmanager.Level#FATAL
* org.jboss.logmanager.Level#ERROR
* org.jboss.logmanager.Level#WARN
* org.jboss.logmanager.Level#INFO
* org.jboss.logmanager.Level#DEBUG
* org.jboss.logmanager.Level#TRACE

In addition, it also supports the standard JDK log levels.

Micrometer MeterBinder implementations discovered on the classpath will be enabled automatically by default.

Suppressing non-application uris is enabled by default.

Micrometer metrics support is enabled by default.

Use this attribute to veto the creation of the default Prometheus MeterRegistry.

Micrometer MeterRegistry implementations discovered on the classpath will be enabled automatically by default.

A valid prefix consists of alphanumeric characters and underscores. Three special constants can be used:

• - the alias of an iterated element suffixed with an underscore is used, e.g. item_hasNext and it_count
• - the alias of an iterated element suffixed with a question mark is used, e.g. item?hasNext and it?count
• - no prefix is used, e.g. hasNext and count

Note that the quarkus.qute.property-not-found-strategy config property is completely ignored if strict rendering is enabled.

By default, `engine.getTemplate("foo")` would result in several lookups: `foo`, `foo.html`, `foo.txt`, etc.

The matched input is the file path relative from the templates directory and the / is used as a path separator.

By default, the hidden files are excluded. The name of a hidden file starts with a dot.

  {@literal @}ApplicationScoped
  public class A {
     {@literal @}RolesAllowed("admin")
     public void methodA() {
         ...
     }
     public void methodB() {
         ...
     }
  }

If not set explicitly, resolved addresses may be cached forever.

A typical example is @javax.ejb.Singleton which is often confused with @javax.inject.Singleton. As a result a component annotated with @javax.ejb.Singleton would be completely ignored. Another example is an inner class annotated with a scope annotation - this component would be again completely ignored.

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

A package string representation can be:

• a full name of the package, i.e. org.acme.foo
• a package name with suffix .*, i.e. org.acme.*, which matches a package that starts with provided value

• If set to all (or true) the container will attempt to remove all unused beans.
• If set to none (or false) no beans will ever be removed even if they are unused (according to the criteria set out below)
• If set to fwk, then all unused beans will be removed, except the unused beans whose classes are declared in the application code

An unused bean:

• is not a built-in bean or interceptor,
• is not eligible for injection to any injection point,
• is not excluded by any extension,
• does not have a name,
• does not declare an observer,
• does not declare any producer which is eligible for injection to any injection point,
• is not directly eligible for injection into any javax.enterprise.inject.Instance injection point

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

• Remove 'final' modifier from classes and methods when a proxy is required.
• Create a no-args constructor if needed.
• Makes private no-args constructors package-private if necessary.

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

We don't make it a list as the args are separated by a space, not a comma.

Artifacts should be configured as a comma separated list of artifact ids, with the group, artifact-id and optional classifier separated by a colon.

WARNING: This config property can only be set in application.properties

This is an advanced option, it should only be used if you have a problem with libraries holding stale state between reloads. Note that if you use this any library that depends on the listed libraries will also need to be reloadable.

This setting has no impact on production builds.

Artifacts should be configured as a comma separated list of artifact ids, with the group, artifact-id and optional classifier separated by a colon.

WARNING: This config property can only be set in application.properties

Set this to true to read configuration from system properties and environment variables only. This only applies to runtime.

Use this option if your terminal does not support ANSI escape sequences.

If this is false results can still be viewed in the dev console.

It is the @Named value of the credentials provider bean. It is used to discriminate if multiple CredentialsProvider beans are available.

For Vault it is: vault-credentials-provider. Not necessary if there is only one credentials provider available.

If not defined, the port will be chosen randomly.

`-1` means batch loading is disabled.

@deprecated #fetch should be used to configure fetching properties.

E.g. `MyISAM` or `InnoDB` for MySQL.

`-1` means batch loading is disabled.

A `0` disables default outer join fetching.

Setting it to true is obviously not recommended in production.

Setting it to true is obviously not recommended in production.

Defaults to `META-INF/orm.xml` if it exists. Pass `no-file` to force Hibernate ORM to ignore `META-INF/orm.xml`.

A `0` disables default outer join fetching.

@deprecated #fetch should be used to configure fetching properties.

[NOTE]
====
Not all customization options exposed by
https://docs.jboss.org/hibernate/stable/orm/javadocs/org/hibernate/boot/MetadataBuilder.html[`org.hibernate.boot.MetadataBuilder`]
will work correctly. Stay clear of options related to classpath scanning in particular.

This setting is exposed mainly to allow registration of types, converters and SQL functions.
====

Valid values are: `none`, `first`, `last`.

Just cherry-pick which entities should be using the cache.

Set this to false to disable all 2nd level caches.

The file is retrieved from the classpath resources,
so it must be located in the resources directory (e.g. `src/main/resources`).

The default value for this setting differs depending on the Quarkus launch mode:

* In dev and test modes, it defaults to `import.sql`.
Simply add an `import.sql` file in the root of your resources directory
and it will be picked up without having to set this property.
Pass `no-file` to force Hibernate ORM to ignore the SQL import file.
* In production mode, it defaults to `no-file`.
It means Hibernate ORM won't try to execute any SQL import file by default.
Pass an explicit value to force Hibernate ORM to execute the SQL import file.

If you need different SQL statements between dev mode, test (`@QuarkusTest`) and in production, use Quarkus
https://quarkus.io/guides/config#configuration-profiles[configuration profiles facility].

[source,property]
.application.properties
----
%dev.quarkus.hibernate-orm.sql-load-script = import-dev.sql
%test.quarkus.hibernate-orm.sql-load-script = import-test.sql
%prod.quarkus.hibernate-orm.sql-load-script = no-file
----

[NOTE]
====
Quarkus supports `.sql` file with SQL statements or comments spread over multiple lines.
Each SQL statement must be terminated by a semicolon.
====

This property only affects the EL feature level of "static" constraint violation messages set through the message attribute of constraint annotations.

In particular, it doesn't affect the default EL feature level for custom violations created programmatically in validator implementations. The feature level for those can only be configured directly in the validator implementation.

If the client requested a supported content-type in request headers (e.g. "Accept: application/json", "Accept: text/html"), Quarkus will use that content type.

Otherwise, it will default to the content type configured here.

The relative paths are relative to the application working directly.

Support for gRPC client metrics will be enabled if Micrometer support is enabled, the gRPC client interfaces are on the classpath and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for gRPC server metrics will be enabled if Micrometer support is enabled, the gRPC server interfaces are on the classpath and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for HTTP client metrics will be enabled if Micrometer support is enabled, the REST client feature is enabled, and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Outbount HTTP client instrumentation will attempt to transform parameterized
resource paths, `/item/123`, into a generic form, `/item/{id}`,
to reduce the cardinality of uri label values.

Patterns specified here will take precedence over those computed
values.

For example, if `/item/\\\\d+=/item/custom` or
`/item/[0-9]+=/item/custom` is specified in this list,
a request to a matching path (`/item/123`) will use the specified
replacement value (`/item/custom`) as the value for the uri label.
Note that backslashes must be double escaped as `\\\\`.

Support for HTTP server metrics will be enabled if Micrometer support is enabled, an extension serving HTTP traffic is enabled, and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Vertx instrumentation will attempt to transform parameterized
resource paths, `/item/123`, into a generic form, `/item/{id}`,
to reduce the cardinality of uri label values.

Patterns specified here will take precedence over those computed
values.

For example, if `/item/\\\\d+=/item/custom` or
`/item/[0-9]+=/item/custom` is specified in this list,
a request to a matching path (`/item/123`) will use the specified
replacement value (`/item/custom`) as the value for the uri label.
Note that backslashes must be double escaped as `\\\\`.

Support for JVM metrics will be enabled if Micrometer support is enabled, and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for Kafka metrics will be enabled if Micrometer support is enabled, the Kafka Consumer or Producer interface is on the classpath and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for MicroProfile Metrics will be enabled if Micrometer
support is enabled and the MicroProfile Metrics dependency is present:

[source,xml]
----

org.eclipse.microprofile.metrics
microprofile-metrics-api

----

The Micrometer extension currently provides a compatibility layer that supports the MP Metrics API,
but metric names and recorded values will be different.
Note that the MP Metrics compatibility layer will move to a different extension in the future.

Support for System metrics will be enabled if Micrometer support is enabled, and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for Vert.x metrics will be enabled if Micrometer support is enabled, Vert.x MetricsOptions is on the classpath and either this value is true, or this value is unset and quarkus.micrometer.binder-enabled-default is true.

Support for Prometheus will be enabled if Micrometer support is enabled, the PrometheusMeterRegistry is on the classpath and either this value is true, or this value is unset and quarkus.micrometer.registry-enabled-default is true.

Use slash (/) as a path separator on all platforms. Globs must not start with slash.

Please refer to #includes for details about the glob syntax.

By default, no resources are excluded.

Example: Given that you have src/main/resources/red.png and src/main/resources/foo/green.png in your source tree and one of your dependency JARs contains bar/blue.png file, with the following configuration

quarkus.native.resources.includes = **/*.png
quarkus.native.resources.excludes = foo/**,**/green.png

Use slash (/) as a path separator on all platforms. Globs must not start with slash.

By default, no resources are included.

Example: Given that you have src/main/resources/ignored.png and src/main/resources/foo/selected.png in your source tree and one of your dependency JARs contains bar/some.txt file, with the following configuration

quarkus.native.resources.includes = foo/**,bar/**/*.txt

Supported glob features

Note that there are three levels of escaping when passing this option via application.properties:

1. application.properties parser
2. MicroProfile Config list converter that splits the comma separated list
3. Glob parser

Note that Quarkus extensions typically include the resources they require by themselves. This option is useful in situations when the built-in functionality is not sufficient.

@deprecated Use the global quarkus.default-locale.

@deprecated Use the global quarkus.default-locale.

Normally, if either a suitable container image to create the AppCDS archive inside of can be determined automatically or if one is explicitly set using the quarkus.package.appcds-builder-image setting, the AppCDS archive is generated by running the JDK contained in the image as a container.

If this option is set to false, a container will not be used to generate the AppCDS archive. Instead, the JDK used to build the application is also used to create the archive. Note that the exact same JDK version must be used to run the application in this case.

Ignored if quarkus.package.create-appcds is set to false.

This parameter is meant to be used in modules where multi-builds have been configured to avoid getting a final package with unused dependencies.

groupId:artifactId:classifier:type

With the classifier and type being optional.

If the type is missing, the artifact is assumed to be of type jar.

This parameter is optional, if absent, no optional dependencies will be included into the final package of the application.

For backward compatibility reasons, this parameter is ignored by default and can be enabled by setting the parameter quarkus.package.filter-optional-dependencies to true.

This parameter is meant to be used in modules where multi-builds have been configured to avoid getting a final package with unused dependencies.

If your application has main classes annotated with io.quarkus.runtime.annotations.QuarkusMain then this can also reference the name given in the annotation, to avoid the need to specify fully qualified names in the config.

The default built in types are 'jar' (which will use 'fast-jar'), 'legacy-jar' for the pre-1.12 default jar packaging, 'uber-jar', 'native' and 'native-sources'.

If this is specified a directory of this name will be created in the jar distribution. Users can place jar files in this directory, and when re-augmentation is performed these will be processed and added to the class-path.

Note that before reaugmentation has been performed these jars will be ignored, and if they are updated the app should be reaugmented again.

This strategy is never used when evaluating section parameters, e.g. {#if foo.name}. In such case, it's the responsibility of the section to handle this situation appropriately.

By default, the NOT_FOUND constant is written to the output. However, in the development mode the PropertyNotFoundStrategy#THROW_EXCEPTION is used by default, i.e. when the strategy is not specified.

An element value must have at least two parts separated by dot. The last part is used to match the property/method name. The prepended parts are used to match the class name. The value * can be used to match any name.

Examples:

• org.acme.Foo.name - exclude the property/method name on the org.acme.Foo class
• org.acme.Foo.* - exclude any property/method on the org.acme.Foo class
• *.age - exclude the property/method age on any class

This value is always resolved relative to quarkus.http.root-path.

The value `/` is not allowed as it blocks the application from serving anything else. By default, this value will be resolved as a path relative to `${quarkus.http.non-application-root-path}`.