Quarkus - All configuration options

If true, this will enable the aws event poll loop within a Quarkus test run. This loop normally only runs in native image. This option is strictly for testing purposes.

The handler name. Handler names are specified on handler classes using the @javax.inject.Named annotation. If this name is unspecified and there is exactly one unnamed implementation of com.amazonaws.services.lambda.runtime.RequestHandler then this unnamed handler will be used. If there is only a single named handler and the name is unspecified then the named handler will be used.

If we create a JDBC datasource for this datasource.

The datasource driver class name

Whether we want to use regular JDBC transactions, XA, or disable all transactional capabilities. When enabling XA you will need a driver implementing javax.sql.XADataSource.

Enable datasource metrics collection. If unspecified, collecting metrics will be enabled by default if the smallrye-metrics extension is active.

The datasource URL

The initial size of the pool. Usually you will want to set the initial size to match at least the minimal size, but this is not enforced so to allow for architectures which prefer a lazy initialization of the connections on boot, while being able to sustain a minimal pool size after boot.

The datasource pool minimum size

The datasource pool maximum size

The interval at which we validate idle connections in the background. Set to 0 to disable background validation.

The timeout before cancelling the acquisition of a new connection

The interval at which we check for connection leaks.

The interval at which we try to remove idle connections.

The max lifetime of a connection.

The transaction isolation level.

When enabled Agroal will be able to produce a warning when a connection is returned to the pool without the application having closed all open statements. This is unrelated with tracking of open connections. Disable for peak performance, but only when there’s high confidence that no leaks are happening.

Query executed when first using a connection.

Query executed to validate a connection.

If we create a JDBC datasource for this datasource.

The datasource driver class name

Whether we want to use regular JDBC transactions, XA, or disable all transactional capabilities. When enabling XA you will need a driver implementing javax.sql.XADataSource.

Enable datasource metrics collection. If unspecified, collecting metrics will be enabled by default if the smallrye-metrics extension is active.

The datasource URL

The initial size of the pool. Usually you will want to set the initial size to match at least the minimal size, but this is not enforced so to allow for architectures which prefer a lazy initialization of the connections on boot, while being able to sustain a minimal pool size after boot.

The datasource pool minimum size

The datasource pool maximum size

The interval at which we validate idle connections in the background. Set to 0 to disable background validation.

The timeout before cancelling the acquisition of a new connection

The interval at which we check for connection leaks.

The interval at which we try to remove idle connections.

The max lifetime of a connection.

The transaction isolation level.

When enabled Agroal will be able to produce a warning when a connection is returned to the pool without the application having closed all open statements. This is unrelated with tracking of open connections. Disable for peak performance, but only when there’s high confidence that no leaks are happening.

Query executed when first using a connection.

Query executed to validate a connection.

List of execution interceptors that will have access to read and modify the request and response objects as they are processed by the AWS SDK. The list should consists of class names which implements software.amazon.awssdk.core.interceptor.ExecutionInterceptor interface.

Type of the sync HTTP client implementation

Enable DynamoDB service endpoint discovery.

The endpoint URI with which the SDK should communicate. If not specified, an appropriate endpoint to be used for DynamoDB service and region.

The amount of time to allow the client to complete the execution of an API call. This timeout covers the entire client execution except for marshalling. This includes request handler execution, all HTTP requests including retries, unmarshalling, etc. This value should always be positive, if present.

The amount of time to wait for the HTTP request to complete before giving up and timing out. This value should always be positive, if present.

An Amazon Web Services region that hosts DynamoDB.

It overrides region provider chain with static value of region with which the DynamoDB client should communicate.

If not set, region is retrieved via the default providers chain in the following order:

See software.amazon.awssdk.regions.Region for available regions.

Configure the credentials provider that should be used to authenticate with AWS.

Available values:

Whether this provider should fetch credentials asynchronously in the background. If this is true, threads are less likely to block, but additional resources are used to maintain the provider.

Whether the provider should reuse the last successful credentials provider in the chain. Reusing the last successful credentials provider will typically return credentials faster than searching through the chain.

AWS Access key id

AWS Secret access key

The name of the profile that should be used by this credentials provider. If not specified, the value in AWS_PROFILE environment variable or aws.profile system property is used and defaults to default name.

Whether the provider should fetch credentials asynchronously in the background. If this is true, threads are less likely to block when credentials are loaded, but additional resources are used to maintain the provider.

The amount of time between when the credentials expire and when the credentials should start to be refreshed. This allows the credentials to be refreshed before they are reported to expire.

The maximum size of the output that can be returned by the external process before an exception is raised.

The command that should be executed to retrieve credentials.

The maximum amount of time to establish a connection before timing out.

The amount of time to wait for data to be transferred over an established, open connection before the connection is timed out.

The amount of time to wait when acquiring a connection from the pool before giving up and timing out.

The maximum amount of time that a connection should be allowed to remain open while idle.

The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency.

The maximum number of connections allowed in the connection pool. Each built HTTP client has its own private connection pool.

Whether the client should send an HTTP expect-continue handshake before each request.

Whether the idle connections in the connection pool should be closed asynchronously. When enabled, connections left idling for longer than quarkus.dynamodb.sync-client.connection-max-idle-time will be closed. This will not close connections currently in use.

Enable HTTP proxy

The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

The username to use when connecting through a proxy.

The password to use when connecting through a proxy.

For NTLM proxies - the Windows domain name to use when authenticating with the proxy.

For NTLM proxies - the Windows workstation name to use when authenticating with the proxy.

Whether to attempt to authenticate preemptively against the proxy server using basic authentication.

The hosts that the client is allowed to access without going through the proxy.

TLS managers provider type.

Available providers:

The maximum number of allowed concurrent requests. For HTTP/1.1 this is the same as max connections. For HTTP/2 the number of connections that will be used depends on the max streams allowed per connection.

The maximum number of pending acquires allowed. Once this exceeds, acquire tries will be failed.

The amount of time to wait for a read on a socket before an exception is thrown. Specify 0 to disable.

The amount of time to wait for a write on a socket before an exception is thrown. Specify 0 to disable.

The amount of time to wait when initially establishing a connection before giving up and timing out.

The amount of time to wait when acquiring a connection from the pool before giving up and timing out.

The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency.

The maximum amount of time that a connection should be allowed to remain open while idle. Currently has no effect if quarkus.dynamodb.async-client.use-idle-connection-reaper is false.

Whether the idle connections in the connection pool should be closed. When enabled, connections left idling for longer than quarkus.dynamodb.async-client.connection-max-idle-time will be closed. This will not close connections currently in use.

The HTTP protocol to use.

The maximum number of concurrent streams for an HTTP/2 connection. This setting is only respected when the HTTP/2 protocol is used. 0 means unlimited.

The SSL Provider to be used in the Netty client. Default is OPENSSL if available, JDK otherwise.

Enable HTTP proxy.

The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

The hosts that the client is allowed to access without going through the proxy.

TLS managers provider type.

Available providers:

Enable the custom configuration of the Netty event loop group.

Number of threads to use for the event loop group. If not set, the default Netty thread count is used (which is double the number of available processors unless the io.netty.eventLoopThreads system property is set.

The thread name prefix for threads created by this thread factory used by event loop group. The prefix will be appended with a number unique to the thread factory and a number unique to the thread. If not specified it defaults to aws-java-sdk-NettyEventLoop

Path to the key store.

Key store type. See the KeyStore section in the Java Cryptography Architecture Standard Algorithm Name Documentation for information about standard keystore types.

Key store password

Path to the key store.

Key store type. See the KeyStore section in the Java Cryptography Architecture Standard Algorithm Name Documentation for information about standard keystore types.

Key store password

Whether or not an health check is published in case the smallrye-health extension is present. If you enable the health check, you must specify the kafka.bootstrap.servers property.

Whether or not a health check is published in case the smallrye-health extension is present (defaults to true).

A unique identifier for this Kafka Streams application.

A comma-separated list of host:port pairs identifying the Kafka bootstrap server(s)

A unique identifier of this application instance, typically in the form host:port.

A comma-separated list of topic names. The pipeline will only be started once all these topics are present in the Kafka cluster.

The resource path within the application artifact to the tika-config.xml file.

Comma separated list of the parsers which must be supported. Most of the document formats recognized by Apache Tika are supported by default but it affects the application memory and native executable sizes. One can list only the required parsers in tika-config.xml to minimize a number of parsers loaded into the memory, but using this property is recommended to achieve both optimizations. Either the abbreviated or full parser class names can be used. Only PDF and OpenDocument format parsers can be listed using the reserved 'pdf' and 'odf' abbreviations. Custom class name abbreviations have to be used for all other parsers. For example: // Only PDF parser is required: quarkus.tika.parsers = pdf // Only PDF and OpenDocument parsers are required: quarkus.tika.parsers = pdf,odf This property will have no effect if the `tikaConfigPath' property has been set.

Controls how the content of the embedded documents is parsed. By default it is appended to the master document content. Setting this property to false makes the content of each of the embedded documents available separately.

Configuration of the individual parsers. For example: quarkus.tika.parsers = pdf,odf quarkus.tika.parser-options.pdf.sort-by-position = true

Full parser class name for a given parser abbreviation. For example: quarkus.tika.parsers = classparser quarkus.tika.parser.classparser = org.apache.tika.parser.asm.ClassParser

If set to true @Inject is automatically added to all non-static fields that are annotated with one of the annotations defined by AutoInjectAnnotationBuildItem.

If set to true, Arc will transform the bytecode of beans containing methods that need to be proxyable but have been declared as final. The transformation is simply a matter of removing final. This ensures that a proxy can be created properly. If the value is set to false, then an exception is thrown at build time indicating that a proxy could not be created because a method was final.

The default naming strategy for ConfigProperties.NamingStrategy. The allowed values are determined by that enum

Whether or not an health check is published in case the smallrye-health extension is present

Artemis connection url

Username for authentication, only used with JMS

Password for authentication, only used with JMS

Cache type.

Minimum total size for the internal data structures. Providing a large enough estimate at construction time avoids the need for expensive resizing operations later, but setting this value unnecessarily high wastes memory.

Maximum number of entries the cache may contain. Note that the cache may evict an entry before this limit is exceeded or temporarily exceed the threshold while evicting. As the cache size grows close to the maximum, the cache evicts entries that are less likely to be used again. For example, the cache may evict an entry because it hasn’t been used recently or very often.

Specifies that each entry should be automatically removed from the cache once a fixed duration has elapsed after the entry’s creation, or the most recent replacement of its value.

Specifies that each entry should be automatically removed from the cache once a fixed duration has elapsed after the entry’s creation, the most recent replacement of its value, or its last read.

Path to the the JVM Dockerfile. If not set ${project.root}/src/main/docker/Dockerfile.jvm will be used If set to an absolute path then the absolute path will be used, otherwise the path will be considered relative to the project root

Path to the the JVM Dockerfile. If not set ${project.root}/src/main/docker/Dockerfile.native will be used If set to an absolute path then the absolute path will be used, otherwise the path will be considered relative to the project root

The base image to be used when a container image is being produced for the jar build

The base image to be used when a container image is being produced for the native binary build

Additional JVM arguments to pass to the JVM when starting the application

Additional arguments to pass when starting the native application

Environment variables to add to the container image

The base image to be used when a container image is being produced for the jar build

The base image to be used when a container image is being produced for the native binary build

Additional JVM arguments to pass to the JVM when starting the application

Additional arguments to pass when starting the native application

The directory where the jar is added during the assemble phase. This is dependant on the s2i image and should be supplied if a non default image is used.

The resulting filename of the jar in the s2i image. This option may be used if the selected s2i image uses a fixed name for the jar.

The directory where the native binary is added during the assemble phase. This is dependant on the s2i image and should be supplied if a non-default image is used.

The resulting filename of the native binary in the s2i image. This option may be used if the selected s2i image uses a fixed name for the native binary.

The build timeout.

The kind of database we will connect to (e.g. h2, postgresql…​).

Whether or not an health check is published in case the smallrye-health extension is present. This is a global setting and is not specific to a datasource.

Whether or not datasource metrics are published in case the smallrye-metrics extension is present. 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 datasource username

The datasource password

The credentials provider name

The credentials provider type. 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.

The kind of database we will connect to (e.g. h2, postgresql…​).

The datasource username

The datasource password

The credentials provider name

The credentials provider type. 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.

Enables or disables the Vert.x cache.

Enables or disabled the Vert.x classpath resource resolver.

The number of event loops. 2 x the number of core by default.

The maximum amount of time the event loop can be blocked. Default is 2s.

The amount of time before a warning is displayed if the event loop is blocked.

The size of the worker thread pool.

The maximum amount of time the worker thread can be blocked. Default is 10s.

The size of the internal thread pool (used for the file system).

Enables the async DNS resolver.

Comma-separated list of the path to the key files (Pem format).

Comma-separated list of the path to the certificate files (Pem format).

Path of the key file (JKS format).

Password of the key file.

Path to the key file (PFX format)

Password of the key.

Comma-separated list of the trust certificate files (Pem format).

Path of the key file (JKS format).

Password of the key file.

Path to the key file (PFX format)

Password of the key.

The accept backlog.

The client authentication.

The connect timeout.

The idle timeout in milliseconds.

The receive buffer size.

The number of reconnection attempts.

The reconnection interval in milliseconds.

Whether or not to reuse the address.

Whether or not to reuse the port.

The send buffer size.

The so linger.

Enables or Disabled SSL.

Whether or not to keep the TCP connection opened (keep-alive).

Configure the TCP no delay.

Configure the traffic class.

Enables or disables the trust all parameter.

The host name.

The port.

The public host name.

The public port.

Enables or disables the clustering.

The ping interval.

The ping reply interval.

Enable or disable native transport

The HTTP root path. All web content will be served relative to this root path.

If basic auth should be enabled. If both basic and form auth is enabled then basic auth will be enabled in silent mode. If no authentication mechanisms are configured basic auth is the default.

If form authentication is enabled

The login page

The error page

The landing page to redirect to if there is no saved page to redirect back to

Option to disable redirect to landingPage if there is no saved page to redirect back to. Form Auth POST is followed by redirect to landingPage by default.

The inactivity (idle) timeout When inactivity timeout is reached, cookie is not renewed and a new login is enforced.

How old a cookie can get before it will be replaced with a new cookie with an updated timeout, also referred to as "renewal-timeout". Note that smaller values will result in slightly more server load (as new encrypted cookies will be generated more often), however larger values affect the inactivity timeout as the timeout is set when a cookie is generated. For example if this is set to 10 minutes, and the inactivity timeout is 30m, if a users last request is when the cookie is 9m old then the actual timeout will happen 21m after the last request, as the timeout is only refreshed when a new cookie is generated. In other words no timeout is tracked on the server side; the timestamp is encoded and encrypted in the cookie itself and it is decrypted and parsed with each request.

The cookie that is used to store the persistent session

The authentication realm

If this is true then only a virtual channel will be set up for vertx web. We have this switch for testing purposes.

Enable the CORS filter.

The HTTP port

The HTTP port used to run tests

The HTTP host

Enable listening to host:port

The HTTPS port

The HTTPS port used to run tests

If this is true then the address, scheme etc will be set from headers forwarded by the proxy server, such as X-Forwarded-For. This should only be set if you are behind a proxy that sets these headers.

If this is true and proxy address forwarding is enabled then the standard Forwarded header will be used, rather than the more common but not standard X-Forwarded-For.

If insecure (i.e. http rather than https) requests are allowed. If this is enabled then http works as normal. redirect will still open the http port, but all requests will be redirected to the HTTPS port. disabled will prevent the HTTP port from opening at all.

Origins allowed for CORS Comma separated list of valid URLs. ex: http://www.quarkus.io,http://localhost:3000 The filter allows any origin if this is not set. default: returns any requested origin as valid

HTTP methods allowed for CORS Comma separated list of valid methods. ex: GET,PUT,POST The filter allows any method if this is not set. default: returns any requested method as valid

HTTP headers allowed for CORS Comma separated list of valid headers. ex: X-Custom,Content-Disposition The filter allows any header if this is not set. default: returns any requested header as valid

HTTP headers exposed in CORS Comma separated list of valid headers. ex: X-Custom,Content-Disposition default: empty

The Access-Control-Max-Age response header value indicating how long the results of a pre-flight request can be cached.

The file path to a server certificate or certificate chain in PEM format.

The file path to the corresponding certificate private key file in PEM format.

An optional key store which holds the certificate information instead of specifying separate files.

An optional parameter to specify type of the key store file. If not given, the type is automatically detected based on the file name.

A parameter to specify the password of the key store file. If not given, the default ("password") is used.

An optional trust store which holds the certificate information of the certificates to trust

An optional parameter to specify type of the trust store file. If not given, the type is automatically detected based on the file name.

A parameter to specify the password of the trust store file.

The cipher suites to use. If none is given, a reasonable default is selected.

The list of protocols to explicitly enable.

Configures the engine to require/request client authentication. NONE, REQUEST, REQUIRED

The number if IO threads used to perform IO. This will be automatically set to a reasonable value based on the number of CPU cores if it is not provided. If this is set to a higher value than the number of Vert.x event loops then it will be capped at the number of event loops. In general this should be controlled by setting quarkus.vertx.event-loops-pool-size, this setting should only be used if you want to limit the number of HTTP io threads to a smaller number than the total number of IO threads.

The the maximum length of all headers.

The maximum size of a request body. Default: no limit.

Http connection idle timeout

Http connection read timeout for blocking IO. This is the maximum amount of time a thread will wait for data, before an IOException will be thrown and the connection closed.

Whether the files sent using multipart/form-data will be stored locally. 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 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.

The directory where the files sent using multipart/form-data should be stored. Either an absolute path or a path relative to the current directory of the application process.

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

Whether the uploaded files should be removed after serving the request. 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.

Whether the body buffer should pre-allocated based on the Content-Length header value. 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

The encryption key that is used to store persistent logins (e.g. for form auth). Logins are stored in a persistent cookie that is encrypted with AES-256 using a key derived from a SHA-256 hash of the key that is provided here. If no key is provided then an in-memory one will be generated, this will change on every restart though so it is not suitable for production environments. This must be more than 16 characters long for security reasons

Enable socket reuse port (linux/macOs native transport only)

Enable tcp quick ack (linux native transport only)

Enable tcp cork (linux native transport only)

Enable tcp fast open (linux native transport only)

Path to a unix domain socket

Enable listening to host:port

The HTTP policy that this permission set is linked to. There are 3 built in policies: permit, deny and authenticated. Role based policies can be defined, and extensions can add their own policies.

The methods that this permission set applies to. If this is not set then they apply to all methods. Note that if a request matches any path from any permission set, but does not match the constraint due to the method not being listed then the request will be denied. Method specific permissions take precedence over matches that do not have any methods set. This means that for example if Quarkus is configured to allow GET and POST requests to /admin to and no other permissions are configured PUT requests to /admin will be denied.

The paths that this permission check applies to. If the path ends in /* then this is treated as a path prefix, otherwise it is treated as an exact match. Matches are done on a length basis, so the most specific path match takes precedence. If multiple permission sets match the same path then explicit methods matches take precedence over over matches without methods set, otherwise the most restrictive permissions are applied.

The roles that are allowed to access resources protected by this policy

The realm name

If the properties store is enabled.

The sql query to find the password

The data source to use

If the clear-password-mapper is enabled.

The index (1 based numbering) of the column containing the clear password

If the bcrypt-password-mapper is enabled.

The index (1 based numbering) of the column containing the password hash

A string referencing the password hash encoding ("BASE64" or "HEX")

The index (1 based numbering) of the column containing the Bcrypt salt

A string referencing the salt encoding ("BASE64" or "HEX")

The index (1 based numbering) of the column containing the Bcrypt iteration count

The index (1 based numbering) of column to map

The target attribute name

The sql query to find the password

The data source to use

The index (1 based numbering) of column to map

The target attribute name

If the clear-password-mapper is enabled.

The index (1 based numbering) of the column containing the clear password

If the bcrypt-password-mapper is enabled.

The index (1 based numbering) of the column containing the password hash

A string referencing the password hash encoding ("BASE64" or "HEX")

The index (1 based numbering) of the column containing the Bcrypt salt

A string referencing the salt encoding ("BASE64" or "HEX")

The index (1 based numbering) of the column containing the Bcrypt iteration count

Determine if the OAuth2 extension is enabled. Enabled by default if you include the elytron-security-oauth2 dependency, so this would be used to disable it.

The OAuth2 client id used to validate the token. Mandatory if the extension is enabled.

The OAuth2 client secret used to validate the token. Mandatory if the extension is enabled.

The OAuth2 introspection endpoint URL used to validate the token and gather the authentication claims. Mandatory if the extension is enabled.

The OAuth2 server certificate file. Warning: this is not supported in native mode where the certificate must be included in the truststore used during the native image generation, see Using SSL With Native Executables.

The claim that is used in the introspection endpoint response to load the roles.

The realm name. This is used when generating a hashed password

Determine whether security via the file realm is enabled.

If the properties are stored in plain text. If this is false (the default) then it is expected that the passwords are of the form HEX( MD5( username ":" realm ":" password ) )

Classpath resource name of properties file containing user to password mappings. See Users.properties.

Classpath resource name of properties file containing user to role mappings. See Roles.properties.

The realm name. This is used when generating a hashed password

If the properties are stored in plain text. If this is false (the default) then it is expected that the passwords are of the form HEX( MD5( username ":" realm ":" password ) )

Determine whether security via the embedded realm is enabled.

The realm users user1=password\nuser2=password2…​ mapping. See Embedded Users.

The realm roles user1=role1,role2,…​\nuser2=role1,role2,…​ mapping See Embedded Roles.

Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix. Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations. Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories.

The maximum number of retries when attempting to connect to the database. After each failed attempt, Flyway will wait 1 second before attempting to connect again, up to the maximum number of times specified by connectRetries.

Comma-separated case-sensitive list of schemas managed by Flyway. The first schema in the list will be automatically set as the default one during the migration. It will also be the one containing the schema history table.

The name of Flyway’s schema history table. By default (single-schema mode) the schema history table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the schema history table is placed in the first schema of the list.

The file name prefix for versioned SQL migrations. Versioned SQL migrations have the following file name structure: prefixVERSIONseparatorDESCRIPTIONsuffix , which using the defaults translates to V1.1__My_description.sql

The file name prefix for repeatable SQL migrations. Repeatable SQL migrations have the following file name structure: prefixSeparatorDESCRIPTIONsuffix , which using the defaults translates to R__My_description.sql

true to execute Flyway clean command automatically when the application starts, false otherwise.

true to execute Flyway automatically when the application starts, false otherwise.

Enable the creation of the history table if it does not exist already.

The initial baseline version.

The description to tag an existing schema with when executing baseline.

Whether to automatically call validate when performing a migration.

Allows migrations to be run "out of order".

Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix. Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations. Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories.

Sets the placeholders to replace in SQL migration scripts.

The maximum number of retries when attempting to connect to the database. After each failed attempt, Flyway will wait 1 second before attempting to connect again, up to the maximum number of times specified by connectRetries.

Comma-separated case-sensitive list of schemas managed by Flyway. The first schema in the list will be automatically set as the default one during the migration. It will also be the one containing the schema history table.

The name of Flyway’s schema history table. By default (single-schema mode) the schema history table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the schema history table is placed in the first schema of the list.

The file name prefix for versioned SQL migrations. Versioned SQL migrations have the following file name structure: prefixVERSIONseparatorDESCRIPTIONsuffix , which using the defaults translates to V1.1__My_description.sql

The file name prefix for repeatable SQL migrations. Repeatable SQL migrations have the following file name structure: prefixSeparatorDESCRIPTIONsuffix , which using the defaults translates to R__My_description.sql

true to execute Flyway clean command automatically when the application starts, false otherwise.

true to execute Flyway automatically when the application starts, false otherwise.

Enable the creation of the history table if it does not exist already.

The initial baseline version.

The description to tag an existing schema with when executing baseline.

Whether to automatically call validate when performing a migration.

Allows migrations to be run "out of order".

Sets the placeholders to replace in SQL migration scripts.

Class name of the Hibernate ORM dialect. The complete list of bundled dialects is available in the Hibernate ORM JavaDoc.

The storage engine to use when the dialect supports multiple storage engines.

E.g. MyISAM or InnoDB for MySQL.

Name of the file containing the SQL statements to execute when Hibernate ORM starts. Its default value differs depending on the Quarkus launch mode:

If you need different SQL statements between dev mode, test (@QuarkusTest) and in production, use Quarkus configuration profiles facility.

The size of the batches used when loading entities and collections.

-1 means batch loading is disabled. This is the default.

Pluggable strategy contract for applying physical naming rules for database object names. Class name of the Hibernate PhysicalNamingStrategy implementation

Pluggable strategy for applying implicit naming rules when an explicit name is not given. Class name of the Hibernate ImplicitNamingStrategy implementation

Whether statistics collection is enabled. If 'metrics.enabled' is true, then the default here is considered true, otherwise the default is false.

Whether or not metrics are published in case the smallrye-metrics extension is present (default to false).

The default in Quarkus is for 2nd level caching to be enabled, and a good implementation is already integrated for you. Just cherry-pick which entities should be using the cache. Set this to false to disable all 2nd level caches.

The maximum size of the query plan cache.

Default precedence of null values in ORDER BY clauses.

Valid values are: none, first, last.

Select whether the database schema is generated or not. drop-and-create is awesome in development mode. Accepted values: none, create, drop-and-create, drop, update.

Whether we should stop on the first error when applying the schema.

The default catalog to use for the database objects.

The default schema to use for the database objects.

The charset of the database.

Whether Hibernate should quote all identifiers.

The time zone pushed to the JDBC driver.

How many rows are fetched at a time by the JDBC driver.

The number of updates (inserts, updates and deletes) that are sent by the JDBC driver at one time for execution.

Show SQL logs and format them nicely. Setting it to true is obviously not recommended in production.

Whether JDBC warnings should be collected and logged.

The maximum time before an object of the cache is considered expired.

The maximum number of objects kept in memory in the cache.

The class or the name of the bean that should be notified of any failure occurring in a background process (mainly index operations). Must implement org.hibernate.search.engine.reporting.FailureHandler.

The strategy to use when loading entities during the execution of a search query.

The fetch size to use when loading entities during the execution of a search query.

The synchronization strategy to use when indexing automatically. Defines how complete indexing should be before resuming the application thread after a database transaction is committed. Available values: Strategy Guarantees when the application thread resumes Throughput Changes applied Changes safe from crash/power loss Changes visible on search ``AutomaticIndexingSynchronizationStrategyNames#ASYNC

Whether to check if dirty properties are relevant to indexing before actually reindexing an entity. When enabled, re-indexing of an entity is skipped if the only changes are on properties that are not used when indexing.

The version of Elasticsearch used in the cluster. As the schema is generated without a connection to the server, this item is mandatory. It doesn’t have to be the exact version (it can be 7 or 7.1 for instance) but it has to be sufficiently precise to choose a model dialect (the one used to generate the schema) compatible with the protocol dialect (the one used to communicate with Elasticsearch). There’s no rule of thumb here as it depends on the schema incompatibilities introduced by Elasticsearch versions. In any case, if there is a problem, you will have an error when Hibernate Search tries to connect to the cluster.

The class or the name of the bean used to configure full text analysis (e.g. analyzers, normalizers).

The list of hosts of the Elasticsearch servers.

The protocol to use when contacting Elasticsearch servers. Set to "https" to enable SSL/TLS.

The username used for authentication.

The password used for authentication.

The connection timeout.

The maximum number of connections to all the Elasticsearch servers.

The maximum number of connections per Elasticsearch server.

Defines if automatic discovery is enabled.

Refresh interval of the node list.

The strategy used for index lifecycle.

The minimal cluster status required.

How long we should wait for the status before failing the bootstrap.

The strategy used for index lifecycle.

The minimal cluster status required.

How long we should wait for the status before failing the bootstrap.

Only useful when defining backends additional backends: the name of the default backend, i.e. the backend that will be assigned to @Indexed entities that do not specify a backend explicitly through @Indexed(backend = …​).

The version of Elasticsearch used in the cluster. As the schema is generated without a connection to the server, this item is mandatory. It doesn’t have to be the exact version (it can be 7 or 7.1 for instance) but it has to be sufficiently precise to choose a model dialect (the one used to generate the schema) compatible with the protocol dialect (the one used to communicate with Elasticsearch). There’s no rule of thumb here as it depends on the schema incompatibilities introduced by Elasticsearch versions. In any case, if there is a problem, you will have an error when Hibernate Search tries to connect to the cluster.

The class or the name of the bean used to configure full text analysis (e.g. analyzers, normalizers).

The list of hosts of the Elasticsearch servers.

The protocol to use when contacting Elasticsearch servers. Set to "https" to enable SSL/TLS.

The username used for authentication.

The password used for authentication.

The connection timeout.

The maximum number of connections to all the Elasticsearch servers.

The maximum number of connections per Elasticsearch server.

Defines if automatic discovery is enabled.

Refresh interval of the node list.

The strategy used for index lifecycle.

The minimal cluster status required.

How long we should wait for the status before failing the bootstrap.

The strategy used for index lifecycle.

The minimal cluster status required.

How long we should wait for the status before failing the bootstrap.

Sets the bounded entry count for near cache. If this value is 0 or less near cache is disabled.

Sets the host name/port to connect to. Each one is separated by a semicolon (eg. host1:11222;host2:11222).

Sets client intelligence used by authentication

Enables or disables authentication

Sets user name used by authentication

Sets password used by authentication

Sets realm used by authentication

Sets server name used by authentication

Sets client subject used by authentication

Sets callback handler used by authentication

Sets SASL mechanism used by authentication

The configured Infinispan embedded xml file which is used by the managed EmbeddedCacheManager and its Caches

Defines if the Jaeger extension is enabled.

The traces endpoint, in case the client should connect directly to the Collector, like http://jaeger-collector:14268/api/traces

Authentication Token to send as "Bearer" to the endpoint

Username to send as part of "Basic" authentication to the endpoint

Password to send as part of "Basic" authentication to the endpoint

The hostname and port for communicating with agent via UDP

Whether the reporter should also log the spans

The reporter’s maximum queue size

The reporter’s flush interval

The sampler type (const, probabilistic, ratelimiting or remote)

The sampler parameter (number)

The host name and port when using the remote controlled sampler

The service name

A comma separated list of name = value tracer level tags, which get added to all reported spans. The value can also refer to an environment variable using the format ${envVarName:default}, where the :default is optional, and identifies a value to be used if the environment variable cannot be found

Comma separated list of formats to use for propagating the trace context. Defaults to the standard Jaeger format. Valid values are jaeger and b3

The sender factory class name

Whether the trace context should be logged.

Adapters will make separate HTTP invocations to the Keycloak server to turn an access code into an access token. This config option defines how many connections to the Keycloak server should be pooled

Enables policy enforcement.

Specifies how policies are enforced.