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_UNLEASH_DEVSERVICES_ENABLED

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

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_PORT

Indicates if the Unleash 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 Unleash starts a new container. The discovery uses the quarkus-dev-service-unleash label. The value is configured using the service-name property. Container sharing is only used in dev mode.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_SHARED

The value of the quarkus-dev-service-unleash 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 Unleash looks for a container with the quarkus-dev-service-unleash 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-unleash label set to the specified value. This property is used when you need multiple shared Unleash servers.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_SERVICE_NAME

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

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_IMAGE_NAME

Helper to define the stop strategy for containers created by DevServices. In particular, we don’t want to actually stop the containers when they have been flagged for reuse, and when the Testcontainers configuration has been explicitly set to allow container reuse. To enable reuse, ass testcontainers.reuse.enable=true in your .testcontainers.properties file, to be stored in your home.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_REUSE

The import data from file during the start.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_IMPORT_FILE

The container image name to use, for container based zeebe simple monitor.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_DB_IMAGE_NAME

The value of the quarkus-dev-service-unleash-db 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 Unleash DB looks for a container with the quarkus-dev-service-unleash-db 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-unleash-db label set to the specified value. This property is used when you need multiple shared Unleash DB servers.

Environment variable: QUARKUS_UNLEASH_DEVSERVICES_DB_SERVICE_NAME

Unleash URL service endpoint

Environment variable: QUARKUS_UNLEASH_URL

Application name

Environment variable: QUARKUS_UNLEASH_APPLICATION

Project name

Environment variable: QUARKUS_UNLEASH_PROJECT

Instance ID.

Environment variable: QUARKUS_UNLEASH_INSTANCE_ID

Disable Unleash metrics

Environment variable: QUARKUS_UNLEASH_DISABLE_METRICS

Application Unleash token

Environment variable: QUARKUS_UNLEASH_TOKEN

Application environment

Environment variable: QUARKUS_UNLEASH_ENVIRONMENT

Fetch toggles interval

Environment variable: QUARKUS_UNLEASH_FETCH_TOGGLES_INTERVAL

Send metrics interval

Environment variable: QUARKUS_UNLEASH_SEND_METRICS_INTERVAL

Backup file

Environment variable: QUARKUS_UNLEASH_BACKUP_FILE

A synchronous fetch on initialisation

Environment variable: QUARKUS_UNLEASH_SYNCHRONOUS_FETCH_ON_INITIALISATION

Enable proxy authentication by JVM properties

Environment variable: QUARKUS_UNLEASH_ENABLE_PROXY_AUTHENTICATION_BY_JVM_PROPERTIES