By Version

Visão Geral dos Dev Services

O Quarkus oferece suporte ao provisionamento automático de serviços não configurados no modo de desenvolvimento e teste. Referimo-nos a esse recurso como Dev Services. Do ponto de vista do desenvolvedor, isso significa que, se você incluir uma extensão e não a configurar, o Quarkus iniciará automaticamente o serviço relevante (geralmente usando Testcontainers nos bastidores) e conectará sua aplicação para usar esse serviço.

Toda essa funcionalidade faz parte dos módulos do deployment do Quarkus e, portanto, não afeta a aplicação de produção de forma alguma. Se quiser desativar todos os Dev Services, você pode usar a propriedade de configuração quarkus.devservices.enabled=false, embora na maioria dos casos isso não seja necessário, pois a simples configuração do serviço fará com que o Dev Service seja desativado automaticamente.

Note que o tempo limite de arranque predefinido é de 60s, se não for suficiente, pode aumentá-lo com a propriedade quarkus.devservices.timeout.

Esta página lista todos os Dev Services que o Quarkus suporta.

Para usar os Dev Services, você geralmente precisa de um ambiente Docker em funcionamento (há suporte para ambientes remotos). Se você não tiver o Docker instalado, precisará configurar seus serviços normalmente.

AMQP

The AMQP Dev Service will be enabled when the quarkus-smallrye-reactive-messaging-amqp extension is present in your application, and the broker address has not been explicitly configured. More information can be found at the AMQP Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.amqp.devservices.enabled` If Dev Services for AMQP has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For AMQP, Dev Services starts a broker unless `amqp-host` or `amqp-port` are set or if all the Reactive Messaging AMQP channel are configured with `host` or `port`. Environment variable: `QUARKUS_AMQP_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.amqp.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_AMQP_DEVSERVICES_PORT` Show more	int
`quarkus.amqp.devservices.image-name` The image to use. Note that only ActiveMQ Artemis images are supported. Specifically, the image repository must end with `artemiscloud/activemq-artemis-broker`. Check https://quay.io/repository/artemiscloud/activemq-artemis-broker to find the available versions. Environment variable: `QUARKUS_AMQP_DEVSERVICES_IMAGE_NAME` Show more	string	`quay.io/artemiscloud/activemq-artemis-broker:0.1.2`
`quarkus.amqp.devservices.extra-args` The value of the `AMQ_EXTRA_ARGS` environment variable to pass to the container. Environment variable: `QUARKUS_AMQP_DEVSERVICES_EXTRA_ARGS` Show more	string	`--no-autotune --mapped --no-fsync`
`quarkus.amqp.devservices.shared` Indicates if the AMQP broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for AMQP starts a new container. The discovery uses the `quarkus-dev-service-amqp` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_AMQP_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.amqp.devservices.service-name` The value of the `quarkus-dev-service-aqmp` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for AMQP looks for a container with the `quarkus-dev-service-amqp` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-amqp` label set to the specified value. This property is used when you need multiple shared AMQP brokers. Environment variable: `QUARKUS_AMQP_DEVSERVICES_SERVICE_NAME` Show more	string	`amqp`

Configuration property

Tipo

Padrão

quarkus.amqp.devservices.enabled

If Dev Services for AMQP has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For AMQP, Dev Services starts a broker unless amqp-host or amqp-port are set or if all the Reactive Messaging AMQP channel are configured with host or port.

Environment variable: QUARKUS_AMQP_DEVSERVICES_ENABLED

booleano

quarkus.amqp.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_AMQP_DEVSERVICES_PORT

int

quarkus.amqp.devservices.image-name

The image to use. Note that only ActiveMQ Artemis images are supported. Specifically, the image repository must end with artemiscloud/activemq-artemis-broker. Check https://quay.io/repository/artemiscloud/activemq-artemis-broker to find the available versions.

Environment variable: QUARKUS_AMQP_DEVSERVICES_IMAGE_NAME

string

quay.io/artemiscloud/activemq-artemis-broker:0.1.2

quarkus.amqp.devservices.extra-args

The value of the AMQ_EXTRA_ARGS environment variable to pass to the container.

Environment variable: QUARKUS_AMQP_DEVSERVICES_EXTRA_ARGS

string

--no-autotune --mapped --no-fsync

quarkus.amqp.devservices.shared

Indicates if the AMQP broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for AMQP starts a new container. The discovery uses the quarkus-dev-service-amqp label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_AMQP_DEVSERVICES_SHARED

booleano

true

quarkus.amqp.devservices.service-name

The value of the quarkus-dev-service-aqmp label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for AMQP looks for a container with the quarkus-dev-service-amqp label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-amqp label set to the specified value. This property is used when you need multiple shared AMQP brokers.

Environment variable: QUARKUS_AMQP_DEVSERVICES_SERVICE_NAME

string

amqp

Apicurio Registry

The Apicurio Dev Service will be enabled when the quarkus-apicurio-registry-avro extension is present in your application, and it’s address has not been explicitly configured. More information can be found at the Apicurio Registry Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.apicurio-registry.devservices.enabled` If Dev Services for Apicurio Registry has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Apicurio Registry, Dev Services starts a registry unless `mp.messaging.connector.smallrye-kafka.apicurio.registry.url` or `mp.messaging.connector.smallrye-kafka.schema.registry.url` is set. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.apicurio-registry.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_PORT` Show more	int
`quarkus.apicurio-registry.devservices.image-name` The Apicurio Registry image to use. Note that only Apicurio Registry 2.x images are supported. Specifically, the image repository must end with `apicurio/apicurio-registry-mem`. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_IMAGE_NAME` Show more	string	`quay.io/apicurio/apicurio-registry-mem:2.2.3.Final`
`quarkus.apicurio-registry.devservices.shared` Indicates if the Apicurio Registry instance managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Apicurio Registry starts a new container. The discovery uses the `quarkus-dev-service-apicurio-registry` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.apicurio-registry.devservices.service-name` The value of the `quarkus-dev-service-apicurio-registry` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Apicurio Registry looks for a container with the `quarkus-dev-service-apicurio-registry` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-apicurio-registry` label set to the specified value. This property is used when you need multiple shared Apicurio Registry instances. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SERVICE_NAME` Show more	string	`apicurio-registry`

Configuration property

Tipo

Padrão

quarkus.apicurio-registry.devservices.enabled

If Dev Services for Apicurio Registry has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Apicurio Registry, Dev Services starts a registry unless mp.messaging.connector.smallrye-kafka.apicurio.registry.url or mp.messaging.connector.smallrye-kafka.schema.registry.url is set.

Environment variable: QUARKUS_APICURIO_REGISTRY_DEVSERVICES_ENABLED

booleano

quarkus.apicurio-registry.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_APICURIO_REGISTRY_DEVSERVICES_PORT

int

quarkus.apicurio-registry.devservices.image-name

The Apicurio Registry image to use. Note that only Apicurio Registry 2.x images are supported. Specifically, the image repository must end with apicurio/apicurio-registry-mem.

Environment variable: QUARKUS_APICURIO_REGISTRY_DEVSERVICES_IMAGE_NAME

string

quay.io/apicurio/apicurio-registry-mem:2.2.3.Final

quarkus.apicurio-registry.devservices.shared

Indicates if the Apicurio Registry instance managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Apicurio Registry starts a new container. The discovery uses the quarkus-dev-service-apicurio-registry label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SHARED

booleano

true

quarkus.apicurio-registry.devservices.service-name

The value of the quarkus-dev-service-apicurio-registry label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Apicurio Registry looks for a container with the quarkus-dev-service-apicurio-registry label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-apicurio-registry label set to the specified value. This property is used when you need multiple shared Apicurio Registry instances.

Environment variable: QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SERVICE_NAME

string

apicurio-registry

Bases de Dados

The database Dev Services will be enabled when a reactive or JDBC datasource extension is present in the application, and the database URL has not been configured. More information can be found at the Databases Dev Services Guide.

O Quarkus fornece Dev Services para todos os bancos de dados compatíveis. A maioria deles é executada em um contêiner, exceto o H2 e o Derby, que são executados no processo. Os Dev Services são compatíveis com drivers JDBC e reativos.

Esses bancos de dados relacionais que estão sendo executados em um contêiner são iniciados usando Testcontainers e suportam "instâncias reutilizáveis"; isso significa que, se você adicionar a propriedade testcontainers.reuse.enable=true no arquivo de configuração do Testcontainers, um arquivo de propriedade chamado .testcontainers.properties na home do usuário, os bancos de dados não serão interrompidos de forma agressiva após cada execução e poderão ser reutilizados.

Nota: se optar por esta funcionalidade, o Quarkus não reiniciará o estado da base de dados entre execuções, a menos que o configure explicitamente.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.datasource.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.datasource.devservices.image-name` The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.datasource.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PORT` Show more	int
`quarkus.datasource.devservices.command` The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_COMMAND` Show more	string
`quarkus.datasource.devservices.db-name` The name of the database to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_DB_NAME` Show more	string
`quarkus.datasource.devservices.username` The username to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_USERNAME` Show more	string
`quarkus.datasource.devservices.password` The password to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PASSWORD` Show more	string
`quarkus.datasource.devservices.container-properties` Generic properties that are passed for additional container configuration. Properties defined here are database specific and are interpreted specifically in each database dev service implementation. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_CONTAINER_PROPERTIES` Show more	`Map<String,String>`
`quarkus.datasource.devservices.properties` Generic properties that are added to the database connection URL. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PROPERTIES` Show more	`Map<String,String>`
`quarkus.datasource."datasource-name".devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_ENABLED` Show more	booleano
`quarkus.datasource."datasource-name".devservices.image-name` The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.datasource."datasource-name".devservices.container-properties` Generic properties that are passed for additional container configuration. Properties defined here are database specific and are interpreted specifically in each database dev service implementation. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_CONTAINER_PROPERTIES` Show more	`Map<String,String>`
`quarkus.datasource."datasource-name".devservices.properties` Generic properties that are added to the database connection URL. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PROPERTIES` Show more	`Map<String,String>`
`quarkus.datasource."datasource-name".devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PORT` Show more	int
`quarkus.datasource."datasource-name".devservices.command` The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_COMMAND` Show more	string
`quarkus.datasource."datasource-name".devservices.db-name` The name of the database to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_DB_NAME` Show more	string
`quarkus.datasource."datasource-name".devservices.username` The username to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_USERNAME` Show more	string
`quarkus.datasource."datasource-name".devservices.password` The password to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PASSWORD` Show more	string

Configuration property

Tipo

Padrão

quarkus.datasource.devservices.enabled

If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_ENABLED

booleano

quarkus.datasource.devservices.image-name

The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_IMAGE_NAME

string

quarkus.datasource.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_PORT

int

quarkus.datasource.devservices.command

The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_COMMAND

string

quarkus.datasource.devservices.db-name

The name of the database to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_DB_NAME

string

quarkus.datasource.devservices.username

The username to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_USERNAME

string

quarkus.datasource.devservices.password

The password to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_PASSWORD

string

quarkus.datasource.devservices.container-properties

Generic properties that are passed for additional container configuration. Properties defined here are database specific and are interpreted specifically in each database dev service implementation.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_CONTAINER_PROPERTIES

Map<String,String>

quarkus.datasource.devservices.properties

Generic properties that are added to the database connection URL.

Environment variable: QUARKUS_DATASOURCE_DEVSERVICES_PROPERTIES

Map<String,String>

quarkus.datasource."datasource-name".devservices.enabled

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_ENABLED

booleano

quarkus.datasource."datasource-name".devservices.image-name

The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_IMAGE_NAME

string

quarkus.datasource."datasource-name".devservices.container-properties

Generic properties that are passed for additional container configuration. Properties defined here are database specific and are interpreted specifically in each database dev service implementation.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_CONTAINER_PROPERTIES

Map<String,String>

quarkus.datasource."datasource-name".devservices.properties

Generic properties that are added to the database connection URL.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PROPERTIES

Map<String,String>

quarkus.datasource."datasource-name".devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PORT

int

quarkus.datasource."datasource-name".devservices.command

The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_COMMAND

string

quarkus.datasource."datasource-name".devservices.db-name

The name of the database to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_DB_NAME

string

quarkus.datasource."datasource-name".devservices.username

The username to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_USERNAME

string

quarkus.datasource."datasource-name".devservices.password

The password to use if this Dev Service supports overriding it.

Environment variable: QUARKUS_DATASOURCE__DATASOURCE_NAME__DEVSERVICES_PASSWORD

string

Kafka

The Kafka Dev Service will be enabled when the quarkus-kafka-client extension is present in your application, and the broker address has not been explicitly configured. More information can be found at the Kafka Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.kafka.devservices.enabled` If Dev Services for Kafka has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Kafka, Dev Services starts a broker unless `kafka.bootstrap.servers` is set or if all the Reactive Messaging Kafka channel are configured with a `bootstrap.servers`. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.kafka.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_PORT` Show more	int
`quarkus.kafka.devservices.image-name` The Kafka container image to use. Only Redpanda and Strimzi images are supported. Default image is Redpanda. Note that Strimzi images are launched in Kraft mode. In order to use a Strimzi image you need to set a compatible image name such as `quay.io/strimzi-test-container/test-container:0.100.0-kafka-3.1.0` or `quay.io/strimzi/kafka:0.27.1-kafka-3.0.0` For Redpanda: See https://vectorized.io/docs/quick-start-docker/ and https://hub.docker.com/r/vectorized/redpanda For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container Environment variable: `QUARKUS_KAFKA_DEVSERVICES_IMAGE_NAME` Show more	string	`docker.io/vectorized/redpanda:v22.1.7`
`quarkus.kafka.devservices.shared` Indicates if the Kafka broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kafka starts a new container. The discovery uses the `quarkus-dev-service-kafka` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.kafka.devservices.service-name` The value of the `quarkus-dev-service-kafka` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Kafka looks for a container with the `quarkus-dev-service-kafka` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-kafka` label set to the specified value. This property is used when you need multiple shared Kafka brokers. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_SERVICE_NAME` Show more	string	`kafka`
`quarkus.kafka.devservices.topic-partitions-timeout` Timeout for admin client calls used in topic creation. Defaults to 2 seconds. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS_TIMEOUT` Show more	Duration	`2S`
`quarkus.kafka.devservices.redpanda.transaction-enabled` Enables transaction support. Also enables the producer idempotence. Find more info about Red Panda transaction support on https://vectorized.io/blog/fast-transactions/. Notice that KIP-447 (producer scalability for exactly once semantic) and KIP-360 (Improve reliability of idempotent/transactional producer) are not supported. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_REDPANDA_TRANSACTION_ENABLED` Show more	booleano	`true`
`quarkus.kafka.devservices.topic-partitions` The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions. The topic creation will not try to re-partition existing topics with different number of partitions. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS` Show more	`Map<String,Integer>`

Configuration property

Tipo

Padrão

quarkus.kafka.devservices.enabled

If Dev Services for Kafka has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Kafka, Dev Services starts a broker unless kafka.bootstrap.servers is set or if all the Reactive Messaging Kafka channel are configured with a bootstrap.servers.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_ENABLED

booleano

quarkus.kafka.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_PORT

int

quarkus.kafka.devservices.image-name

The Kafka container image to use. Only Redpanda and Strimzi images are supported. Default image is Redpanda. Note that Strimzi images are launched in Kraft mode. In order to use a Strimzi image you need to set a compatible image name such as quay.io/strimzi-test-container/test-container:0.100.0-kafka-3.1.0 or quay.io/strimzi/kafka:0.27.1-kafka-3.0.0 For Redpanda: See https://vectorized.io/docs/quick-start-docker/ and https://hub.docker.com/r/vectorized/redpanda For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container

Environment variable: QUARKUS_KAFKA_DEVSERVICES_IMAGE_NAME

string

docker.io/vectorized/redpanda:v22.1.7

quarkus.kafka.devservices.shared

Indicates if the Kafka broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kafka starts a new container. The discovery uses the quarkus-dev-service-kafka label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_SHARED

booleano

true

quarkus.kafka.devservices.service-name

The value of the quarkus-dev-service-kafka label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Kafka looks for a container with the quarkus-dev-service-kafka label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-kafka label set to the specified value. This property is used when you need multiple shared Kafka brokers.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_SERVICE_NAME

string

kafka

quarkus.kafka.devservices.topic-partitions-timeout

Timeout for admin client calls used in topic creation. Defaults to 2 seconds.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS_TIMEOUT

Duration

2S

quarkus.kafka.devservices.redpanda.transaction-enabled

Enables transaction support. Also enables the producer idempotence. Find more info about Red Panda transaction support on https://vectorized.io/blog/fast-transactions/. Notice that KIP-447 (producer scalability for exactly once semantic) and KIP-360 (Improve reliability of idempotent/transactional producer) are not supported.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_REDPANDA_TRANSACTION_ENABLED

booleano

true

quarkus.kafka.devservices.topic-partitions

The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, quarkus.kafka.devservices.topic-partitions.test=2 will create a topic named test with 2 partitions. The topic creation will not try to re-partition existing topics with different number of partitions.

Environment variable: QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS

Map<String,Integer>

About the Duration format

The format for durations uses the standard java.time.Duration format. You can learn more about it in the Duration#parse() javadoc.

You can also provide duration values starting with a number. In this case, if the value consists only of a number, the converter treats the value as seconds. Otherwise, PT is implicitly prepended to the value to obtain a standard java.time.Duration format.

Keycloak

The Keycloak Dev Service will be enabled when the quarkus-oidc extension is present in your application, and the server address has not been explicitly configured. More information can be found at the OIDC Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.keycloak.devservices.enabled` If DevServices has been explicitly enabled or disabled. When DevServices is enabled Quarkus will attempt to automatically configure and start Keycloak when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_ENABLED` Show more	booleano	`true`
`quarkus.keycloak.devservices.image-name` The container image name to use, for container based DevServices providers. Image with a Quarkus based distribution is used by default. Image with a WildFly based distribution can be selected instead, for example: 'quay.io/keycloak/keycloak:19.0.1-legacy'. Note Keycloak Quarkus and Keycloak WildFly images are initialized differently. By default, Dev Services for Keycloak will assume it is a Keycloak Quarkus image if the image version does not end with a '-legacy' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME` Show more	string	`quay.io/keycloak/keycloak:19.0.1`
`quarkus.keycloak.devservices.keycloak-x-image` If Keycloak-X image is used. By default, Dev Services for Keycloak will assume a Keycloak-X image is used if the image name contains a 'keycloak-x' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check which may be necessary if you build custom Keycloak-X or Keycloak images. You do not need to set this property if the default check works. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_KEYCLOAK_X_IMAGE` Show more	booleano
`quarkus.keycloak.devservices.shared` Indicates if the Keycloak container managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Keycloak starts a new container. The discovery uses the `quarkus-dev-service-label` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.keycloak.devservices.service-name` The value of the `quarkus-dev-service-keycloak` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Keycloak looks for a container with the `quarkus-dev-service-keycloak` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-keycloak` label set to the specified value. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SERVICE_NAME` Show more	string	`quarkus`
`quarkus.keycloak.devservices.realm-path` The class or file system path to a Keycloak realm file which will be used to initialize Keycloak. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_REALM_PATH` Show more	string
`quarkus.keycloak.devservices.java-opts` The JAVA_OPTS passed to the keycloak JVM Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_JAVA_OPTS` Show more	string
`quarkus.keycloak.devservices.show-logs` Show Keycloak log messages with a "Keycloak:" prefix. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SHOW_LOGS` Show more	booleano	`false`
`quarkus.keycloak.devservices.start-command` Keycloak start command. Use this property to experiment with Keycloak start options, see `https://www.keycloak.org/server/all-config`. Note it will be ignored when loading legacy Keycloak WildFly images. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_START_COMMAND` Show more	string
`quarkus.keycloak.devservices.realm-name` The Keycloak realm name. This property will be used to create the realm if the realm file pointed to by the 'realm-path' property does not exist, default value is 'quarkus' in this case. If the realm file pointed to by the 'realm-path' property exists then it is still recommended to set this property for Dev Services for Keycloak to avoid parsing the realm file in order to determine the realm name. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_REALM_NAME` Show more	string
`quarkus.keycloak.devservices.create-realm` Indicates if the Keycloak realm has to be created when the realm file pointed to by the 'realm-path' property does not exist. Disable it if you’d like to create a realm using Keycloak Administration Console or Keycloak Admin API from `io.quarkus.test.common.QuarkusTestResourceLifecycleManager`. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_CREATE_REALM` Show more	booleano	`true`
`quarkus.keycloak.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_PORT` Show more	int
`quarkus.keycloak.devservices.users` The Keycloak users map containing the username and password pairs. If this map is empty then two users, 'alice' and 'bob' with the passwords matching their names will be created. This property will be used to create the Keycloak users if the realm file pointed to by the 'realm-path' property does not exist. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_USERS` Show more	`Map<String,String>`
`quarkus.keycloak.devservices.roles` The Keycloak user roles. If this map is empty then a user named 'alice' will get 'admin' and 'user' roles and all other users will get a 'user' role. This property will be used to create the Keycloak roles if the realm file pointed to by the 'realm-path' property does not exist. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_ROLES` Show more	`Map<String,List<String>>`

Configuration property

Tipo

Padrão

quarkus.keycloak.devservices.enabled

If DevServices has been explicitly enabled or disabled. When DevServices is enabled Quarkus will attempt to automatically configure and start Keycloak when running in Dev or Test mode and when Docker is running.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_ENABLED

booleano

true

quarkus.keycloak.devservices.image-name

The container image name to use, for container based DevServices providers. Image with a Quarkus based distribution is used by default. Image with a WildFly based distribution can be selected instead, for example: 'quay.io/keycloak/keycloak:19.0.1-legacy'. Note Keycloak Quarkus and Keycloak WildFly images are initialized differently. By default, Dev Services for Keycloak will assume it is a Keycloak Quarkus image if the image version does not end with a '-legacy' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME

string

quay.io/keycloak/keycloak:19.0.1

quarkus.keycloak.devservices.keycloak-x-image

If Keycloak-X image is used. By default, Dev Services for Keycloak will assume a Keycloak-X image is used if the image name contains a 'keycloak-x' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check which may be necessary if you build custom Keycloak-X or Keycloak images. You do not need to set this property if the default check works.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_KEYCLOAK_X_IMAGE

booleano

quarkus.keycloak.devservices.shared

Indicates if the Keycloak container managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Keycloak starts a new container. The discovery uses the quarkus-dev-service-label label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_SHARED

booleano

true

quarkus.keycloak.devservices.service-name

The value of the quarkus-dev-service-keycloak label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Keycloak looks for a container with the quarkus-dev-service-keycloak label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-keycloak label set to the specified value. Container sharing is only used in dev mode.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_SERVICE_NAME

string

quarkus

quarkus.keycloak.devservices.realm-path

The class or file system path to a Keycloak realm file which will be used to initialize Keycloak.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_REALM_PATH

string

quarkus.keycloak.devservices.java-opts

The JAVA_OPTS passed to the keycloak JVM

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_JAVA_OPTS

string

quarkus.keycloak.devservices.show-logs

Show Keycloak log messages with a "Keycloak:" prefix.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_SHOW_LOGS

booleano

false

quarkus.keycloak.devservices.start-command

Keycloak start command. Use this property to experiment with Keycloak start options, see https://www.keycloak.org/server/all-config. Note it will be ignored when loading legacy Keycloak WildFly images.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_START_COMMAND

string

quarkus.keycloak.devservices.realm-name

The Keycloak realm name. This property will be used to create the realm if the realm file pointed to by the 'realm-path' property does not exist, default value is 'quarkus' in this case. If the realm file pointed to by the 'realm-path' property exists then it is still recommended to set this property for Dev Services for Keycloak to avoid parsing the realm file in order to determine the realm name.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_REALM_NAME

string

quarkus.keycloak.devservices.create-realm

Indicates if the Keycloak realm has to be created when the realm file pointed to by the 'realm-path' property does not exist. Disable it if you’d like to create a realm using Keycloak Administration Console or Keycloak Admin API from io.quarkus.test.common.QuarkusTestResourceLifecycleManager.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_CREATE_REALM

booleano

true

quarkus.keycloak.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_PORT

int

quarkus.keycloak.devservices.users

The Keycloak users map containing the username and password pairs. If this map is empty then two users, 'alice' and 'bob' with the passwords matching their names will be created. This property will be used to create the Keycloak users if the realm file pointed to by the 'realm-path' property does not exist.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_USERS

Map<String,String>

quarkus.keycloak.devservices.roles

The Keycloak user roles. If this map is empty then a user named 'alice' will get 'admin' and 'user' roles and all other users will get a 'user' role. This property will be used to create the Keycloak roles if the realm file pointed to by the 'realm-path' property does not exist.

Environment variable: QUARKUS_KEYCLOAK_DEVSERVICES_ROLES

Map<String,List<String>>

Kogito

The Kogito Dev Service will be enabled when either kogito-quarkus or kogito-quarkus-processes extension is present in your application. More information can be found at the Kogito Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.kogito.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a Data Index when running in Dev mode. Show more	booleano	verdadeiro
`quarkus.kogito.devservices.image-name` The container image name to use. Show more	string	quay.io/kiegroup/kogito-data-index-ephemeral
`quarkus.kogito.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Show more	int	8180
`quarkus.kogito.devservices.shared` Indicates if the Data Index instance managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kogito starts a new container. The discovery uses the `kogito-dev-service-data-index` label. The value is configured using the service-name property. Container sharing is only used in dev mode. Show more	booleano	verdadeiro
`quarkus.kogito.devservices.service-name` The value of the `kogito-dev-service-data-index` label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Kogito looks for a container with the `kogito-dev-service-data-index` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `kogito-dev-service-data-index` label set to the specified value. This property is used when you need multiple shared Data Index instances. Show more	string	kogito-data-index

Configuration property

Tipo

Padrão

quarkus.kogito.devservices.enabled

booleano

verdadeiro

quarkus.kogito.devservices.image-name

The container image name to use.

string

quay.io/kiegroup/kogito-data-index-ephemeral

quarkus.kogito.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

int

8180

quarkus.kogito.devservices.shared

Indicates if the Data Index instance managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kogito starts a new container. The discovery uses the kogito-dev-service-data-index label. The value is configured using the service-name property. Container sharing is only used in dev mode.

booleano

verdadeiro

quarkus.kogito.devservices.service-name

The value of the kogito-dev-service-data-index label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Kogito looks for a container with the kogito-dev-service-data-index label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the kogito-dev-service-data-index label set to the specified value. This property is used when you need multiple shared Data Index instances.

string

kogito-data-index

MongoDB

The MongoDB Dev Service will be enabled when the quarkus-mongodb-client extension is present in your application, and the server address has not been explicitly configured. More information can be found at the MongoDB Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.mongodb.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.mongodb.devservices.image-name` The container image name to use, for container based DevServices providers. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.mongodb.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_PORT` Show more	int
`quarkus.mongodb.devservices.properties` Generic properties that are added to the connection URL. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_PROPERTIES` Show more	`Map<String,String>`

Configuration property

Tipo

Padrão

quarkus.mongodb.devservices.enabled

Environment variable: QUARKUS_MONGODB_DEVSERVICES_ENABLED

booleano

quarkus.mongodb.devservices.image-name

The container image name to use, for container based DevServices providers.

Environment variable: QUARKUS_MONGODB_DEVSERVICES_IMAGE_NAME

string

quarkus.mongodb.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_MONGODB_DEVSERVICES_PORT

int

quarkus.mongodb.devservices.properties

Generic properties that are added to the connection URL.

Environment variable: QUARKUS_MONGODB_DEVSERVICES_PROPERTIES

Map<String,String>

RabbitMQ

The RabbitMQ Dev Service will be enabled when the quarkus-smallrye-reactive-messaging-rabbitmq extension is present in your application, and the broker address has not been explicitly configured. More information can be found at the RabbitMQ Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.rabbitmq.devservices.enabled` If Dev Services for RabbitMQ has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For RabbitMQ, Dev Services starts a broker unless `rabbitmq-host` or `rabbitmq-port` are set or if all the Reactive Messaging RabbitMQ channel are configured with `host` or `port`. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.rabbitmq.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_PORT` Show more	int
`quarkus.rabbitmq.devservices.http-port` Optional fixed port for the RabbitMQ management plugin. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_HTTP_PORT` Show more	int
`quarkus.rabbitmq.devservices.image-name` The image to use. Note that only official RabbitMQ images are supported. Specifically, the image repository must end with `rabbitmq`. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_IMAGE_NAME` Show more	string	`rabbitmq:3.9-management`
`quarkus.rabbitmq.devservices.shared` Indicates if the RabbitMQ broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for RabbitMQ starts a new container. The discovery uses the `quarkus-dev-service-rabbitmq` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.rabbitmq.devservices.service-name` The value of the `quarkus-dev-service-rabbitmq` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for RabbitMQ looks for a container with the `quarkus-dev-service-rabbitmq` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-rabbitmq` label set to the specified value. This property is used when you need multiple shared RabbitMQ brokers. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_SERVICE_NAME` Show more	string	`rabbitmq`
`quarkus.rabbitmq.devservices.exchanges."exchanges".type` Type of exchange: direct, topic, headers, fanout, etc. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__TYPE` Show more	string	`direct`
`quarkus.rabbitmq.devservices.exchanges."exchanges".auto-delete` Should the exchange be deleted when all queues are finished using it? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__AUTO_DELETE` Show more	booleano	`false`
`quarkus.rabbitmq.devservices.exchanges."exchanges".durable` Should the exchange remain after restarts? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__DURABLE` Show more	booleano	`false`
`quarkus.rabbitmq.devservices.exchanges."exchanges".arguments` Extra arguments for the exchange definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__ARGUMENTS` Show more	`Map<String,String>`
`quarkus.rabbitmq.devservices.queues."queues".auto-delete` Should the queue be deleted when all consumers are finished using it? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__AUTO_DELETE` Show more	booleano	`false`
`quarkus.rabbitmq.devservices.queues."queues".durable` Should the queue remain after restarts? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__DURABLE` Show more	booleano	`false`
`quarkus.rabbitmq.devservices.queues."queues".arguments` Extra arguments for the queue definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__ARGUMENTS` Show more	`Map<String,String>`
`quarkus.rabbitmq.devservices.bindings."bindings".source` Source exchange to bind to. Defaults to name of binding instance. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__SOURCE` Show more	string
`quarkus.rabbitmq.devservices.bindings."bindings".routing-key` Routing key specification for the source exchange. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ROUTING_KEY` Show more	string	`#`
`quarkus.rabbitmq.devservices.bindings."bindings".destination` Destination exchange or queue to bind to. Defaults to name of binding instance. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION` Show more	string
`quarkus.rabbitmq.devservices.bindings."bindings".destination-type` Destination type for binding: queue, exchange, etc. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION_TYPE` Show more	string	`queue`
`quarkus.rabbitmq.devservices.bindings."bindings".arguments` Extra arguments for the binding definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ARGUMENTS` Show more	`Map<String,String>`

Configuration property

Tipo

Padrão

quarkus.rabbitmq.devservices.enabled

If Dev Services for RabbitMQ has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For RabbitMQ, Dev Services starts a broker unless rabbitmq-host or rabbitmq-port are set or if all the Reactive Messaging RabbitMQ channel are configured with host or port.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_ENABLED

booleano

quarkus.rabbitmq.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_PORT

int

quarkus.rabbitmq.devservices.http-port

Optional fixed port for the RabbitMQ management plugin. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_HTTP_PORT

int

quarkus.rabbitmq.devservices.image-name

The image to use. Note that only official RabbitMQ images are supported. Specifically, the image repository must end with rabbitmq.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_IMAGE_NAME

string

rabbitmq:3.9-management

quarkus.rabbitmq.devservices.shared

Indicates if the RabbitMQ broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for RabbitMQ starts a new container. The discovery uses the quarkus-dev-service-rabbitmq label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_SHARED

booleano

true

quarkus.rabbitmq.devservices.service-name

The value of the quarkus-dev-service-rabbitmq label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for RabbitMQ looks for a container with the quarkus-dev-service-rabbitmq label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-rabbitmq label set to the specified value. This property is used when you need multiple shared RabbitMQ brokers.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_SERVICE_NAME

string

rabbitmq

quarkus.rabbitmq.devservices.exchanges."exchanges".type

Type of exchange: direct, topic, headers, fanout, etc.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__TYPE

string

direct

quarkus.rabbitmq.devservices.exchanges."exchanges".auto-delete

Should the exchange be deleted when all queues are finished using it?

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__AUTO_DELETE

booleano

false

quarkus.rabbitmq.devservices.exchanges."exchanges".durable

Should the exchange remain after restarts?

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__DURABLE

booleano

false

quarkus.rabbitmq.devservices.exchanges."exchanges".arguments

Extra arguments for the exchange definition.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__ARGUMENTS

Map<String,String>

quarkus.rabbitmq.devservices.queues."queues".auto-delete

Should the queue be deleted when all consumers are finished using it?

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__AUTO_DELETE

booleano

false

quarkus.rabbitmq.devservices.queues."queues".durable

Should the queue remain after restarts?

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__DURABLE

booleano

false

quarkus.rabbitmq.devservices.queues."queues".arguments

Extra arguments for the queue definition.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__ARGUMENTS

Map<String,String>

quarkus.rabbitmq.devservices.bindings."bindings".source

Source exchange to bind to. Defaults to name of binding instance.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__SOURCE

string

quarkus.rabbitmq.devservices.bindings."bindings".routing-key

Routing key specification for the source exchange.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ROUTING_KEY

string

#

quarkus.rabbitmq.devservices.bindings."bindings".destination

Destination exchange or queue to bind to. Defaults to name of binding instance.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION

string

quarkus.rabbitmq.devservices.bindings."bindings".destination-type

Destination type for binding: queue, exchange, etc.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION_TYPE

string

queue

quarkus.rabbitmq.devservices.bindings."bindings".arguments

Extra arguments for the binding definition.

Environment variable: QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ARGUMENTS

Map<String,String>

Redis

The Redis Dev Service will be enabled when the quarkus-redis-client extension is present in your application, and the server address has not been explicitly configured. More information can be found at the Redis Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.redis.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_REDIS_DEVSERVICES_ENABLED` Show more	booleano	`true`
`quarkus.redis.devservices.image-name` The container image name to use, for container based DevServices providers. Environment variable: `QUARKUS_REDIS_DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.redis.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_REDIS_DEVSERVICES_PORT` Show more	int
`quarkus.redis.devservices.shared` Indicates if the Redis server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Redis starts a new container. The discovery uses the `quarkus-dev-service-redis` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_REDIS_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.redis.devservices.service-name` The value of the `quarkus-dev-service-redis` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Redis looks for a container with the `quarkus-dev-service-redis` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-redis` label set to the specified value. This property is used when you need multiple shared Redis servers. Environment variable: `QUARKUS_REDIS_DEVSERVICES_SERVICE_NAME` Show more	string	`redis`
`quarkus.redis."additional-redis-clients".devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_ENABLED` Show more	booleano	`true`
`quarkus.redis."additional-redis-clients".devservices.image-name` The container image name to use, for container based DevServices providers. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.redis."additional-redis-clients".devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_PORT` Show more	int
`quarkus.redis."additional-redis-clients".devservices.shared` Indicates if the Redis server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Redis starts a new container. The discovery uses the `quarkus-dev-service-redis` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.redis."additional-redis-clients".devservices.service-name` The value of the `quarkus-dev-service-redis` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Redis looks for a container with the `quarkus-dev-service-redis` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-redis` label set to the specified value. This property is used when you need multiple shared Redis servers. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SERVICE_NAME` Show more	string	`redis`

Configuration property

Tipo

Padrão

quarkus.redis.devservices.enabled

Environment variable: QUARKUS_REDIS_DEVSERVICES_ENABLED

booleano

true

quarkus.redis.devservices.image-name

The container image name to use, for container based DevServices providers.

Environment variable: QUARKUS_REDIS_DEVSERVICES_IMAGE_NAME

string

quarkus.redis.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_REDIS_DEVSERVICES_PORT

int

quarkus.redis.devservices.shared

Indicates if the Redis server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Redis starts a new container. The discovery uses the quarkus-dev-service-redis label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_REDIS_DEVSERVICES_SHARED

booleano

true

quarkus.redis.devservices.service-name

The value of the quarkus-dev-service-redis label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Redis looks for a container with the quarkus-dev-service-redis label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-redis label set to the specified value. This property is used when you need multiple shared Redis servers.

Environment variable: QUARKUS_REDIS_DEVSERVICES_SERVICE_NAME

string

redis

quarkus.redis."additional-redis-clients".devservices.enabled

Environment variable: QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_ENABLED

booleano

true

quarkus.redis."additional-redis-clients".devservices.image-name

The container image name to use, for container based DevServices providers.

Environment variable: QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_IMAGE_NAME

string

quarkus.redis."additional-redis-clients".devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_PORT

int

quarkus.redis."additional-redis-clients".devservices.shared

Environment variable: QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SHARED

booleano

true

quarkus.redis."additional-redis-clients".devservices.service-name

Environment variable: QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SERVICE_NAME

string

redis

Vault

The Vault Dev Service will be enabled when the quarkus-vault extension is present in your application, and the server address has not been explicitly configured. More information can be found at the Vault Guide.

Neo4j

The Neo4j Dev Service will be enabled when the quarkus-neo4j extension is present in your application, and the server address has not been explicitly configured. More information can be found at the Neo4j Guide.

Infinispan

The Infinispan Dev Service will be enabled when the quarkus-infinispan-client extension is present in your application, and the server address has not been explicitly configured. More information can be found at the Infinispan Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.infinispan-client.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ENABLED` Show more	booleano	`true`
`quarkus.infinispan-client.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_PORT` Show more	int
`quarkus.infinispan-client.devservices.shared` Indicates if the Infinispan server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Infinispan starts a new container. The discovery uses the `quarkus-dev-service-infinispan` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.infinispan-client.devservices.service-name` The value of the `quarkus-dev-service-infinispan` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Infinispan looks for a container with the `quarkus-dev-service-infinispan` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-infinispan` label set to the specified value. This property is used when you need multiple shared Infinispan servers. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SERVICE_NAME` Show more	string	`infinispan`
`quarkus.infinispan-client.devservices.image-name` The image to use. Note that only official Infinispan images are supported. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_IMAGE_NAME` Show more	string
`quarkus.infinispan-client.devservices.artifacts` List of the artifacts to automatically download and add to the Infinispan server libraries. For example a Maven coordinate (org.postgresql:postgresql:42.3.1) or a dependency location url. If an invalid value is passed, the Infinispan server will throw an error when trying to start. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ARTIFACTS` Show more	list of string

Configuration property

Tipo

Padrão

quarkus.infinispan-client.devservices.enabled

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ENABLED

booleano

true

quarkus.infinispan-client.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_PORT

int

quarkus.infinispan-client.devservices.shared

Indicates if the Infinispan server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Infinispan starts a new container. The discovery uses the quarkus-dev-service-infinispan label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SHARED

booleano

true

quarkus.infinispan-client.devservices.service-name

The value of the quarkus-dev-service-infinispan label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Infinispan looks for a container with the quarkus-dev-service-infinispan label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-infinispan label set to the specified value. This property is used when you need multiple shared Infinispan servers.

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SERVICE_NAME

string

infinispan

quarkus.infinispan-client.devservices.image-name

The image to use. Note that only official Infinispan images are supported.

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_IMAGE_NAME

string

quarkus.infinispan-client.devservices.artifacts

List of the artifacts to automatically download and add to the Infinispan server libraries. For example a Maven coordinate (org.postgresql:postgresql:42.3.1) or a dependency location url. If an invalid value is passed, the Infinispan server will throw an error when trying to start.

Environment variable: QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ARTIFACTS

list of string

Elasticsearch

The Elasticsearch Dev Service will be enabled when one of the Elasticsearch based extensions (Elasticsearch client or Hibernate Search ORM Elasticsearch) is present in your application, and the server address has not been explicitly configured. More information can be found at the Elasticsearch Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Tipo	Padrão
`quarkus.elasticsearch.devservices.enabled` If Dev Services for Elasticsearch has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Elasticsearch, Dev Services starts a server unless `quarkus.elasticsearch.hosts` is set. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_ENABLED` Show more	booleano
`quarkus.elasticsearch.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_PORT` Show more	int
`quarkus.elasticsearch.devservices.image-name` The Elasticsearch container image to use. Defaults to the elasticsearch image provided by Elastic. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_IMAGE_NAME` Show more	string	`docker.elastic.co/elasticsearch/elasticsearch:7.17.0`
`quarkus.elasticsearch.devservices.java-opts` The value for the ES_JAVA_OPTS env variable. Defaults to setting the heap to 1GB. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_JAVA_OPTS` Show more	string	`-Xmx1g`
`quarkus.elasticsearch.devservices.shared` Indicates if the Elasticsearch server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Elasticsearch starts a new container. The discovery uses the `quarkus-dev-service-elasticsearch` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_SHARED` Show more	booleano	`true`
`quarkus.elasticsearch.devservices.service-name` The value of the `quarkus-dev-service-elasticsearch` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Elasticsearch looks for a container with the `quarkus-dev-service-elasticsearch` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise it starts a new container with the `quarkus-dev-service-elasticsearch` label set to the specified value. This property is used when you need multiple shared Elasticsearch servers. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_SERVICE_NAME` Show more	string	`elasticsearch`

Configuration property

Tipo

Padrão

quarkus.elasticsearch.devservices.enabled

If Dev Services for Elasticsearch has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Elasticsearch, Dev Services starts a server unless quarkus.elasticsearch.hosts is set.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_ENABLED

booleano

quarkus.elasticsearch.devservices.port

Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_PORT

int

quarkus.elasticsearch.devservices.image-name

The Elasticsearch container image to use. Defaults to the elasticsearch image provided by Elastic.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_IMAGE_NAME

string

docker.elastic.co/elasticsearch/elasticsearch:7.17.0

quarkus.elasticsearch.devservices.java-opts

The value for the ES_JAVA_OPTS env variable. Defaults to setting the heap to 1GB.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_JAVA_OPTS

string

-Xmx1g

quarkus.elasticsearch.devservices.shared

Indicates if the Elasticsearch server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Elasticsearch starts a new container. The discovery uses the quarkus-dev-service-elasticsearch label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_SHARED

booleano

true

quarkus.elasticsearch.devservices.service-name

The value of the quarkus-dev-service-elasticsearch label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Elasticsearch looks for a container with the quarkus-dev-service-elasticsearch label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise it starts a new container with the quarkus-dev-service-elasticsearch label set to the specified value. This property is used when you need multiple shared Elasticsearch servers.

Environment variable: QUARKUS_ELASTICSEARCH_DEVSERVICES_SERVICE_NAME

string

elasticsearch

AMQP
Apicurio Registry
Bases de Dados
Kafka
Keycloak
Kogito
MongoDB
RabbitMQ
Redis
Vault
Neo4j
Infinispan
Elasticsearch