quarkus-solace.adoc

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

Configuration property	Type	Default
[lock] quarkus.solace.metrics.enabled Whether a metrics is enabled in case the micrometer is present. Environment variable: QUARKUS_SOLACE_METRICS_ENABLED	boolean	true
[lock] quarkus.solace.health.enabled Whether the liveness health check should be exposed if the smallrye-health extension is present. Environment variable: QUARKUS_SOLACE_HEALTH_ENABLED	boolean	true
[lock] quarkus.solace.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 the Solace broker when running in Dev or Test mode and when Docker is running. Environment variable: QUARKUS_SOLACE_DEVSERVICES_ENABLED	boolean	true
[lock] quarkus.solace.devservices.image-name The container image name to use, for container based DevServices providers. Environment variable: QUARKUS_SOLACE_DEVSERVICES_IMAGE_NAME	string
[lock] quarkus.solace.devservices.shared Indicates if the Solace 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 Solace starts a new container. The discovery uses the quarkus-dev-service-solace label. The value is configured using the service-name property. Container sharing is only used in dev mode. Environment variable: QUARKUS_SOLACE_DEVSERVICES_SHARED	boolean	true
[lock] quarkus.solace.devservices.service-name The value of the quarkus-dev-service-solace 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 Solace looks for a container with the quarkus-dev-service-solace 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-solace label set to the specified value. This property is used when you need multiple shared Solace broker. Environment variable: QUARKUS_SOLACE_DEVSERVICES_SERVICE_NAME	string	solace
quarkus.solace.host The Solace host (hostname:port) Environment variable: QUARKUS_SOLACE_HOST	string	required [exclamation circle]
quarkus.solace.vpn The Solace VPN Environment variable: QUARKUS_SOLACE_VPN	string	required [exclamation circle]
[lock] quarkus.solace.devservices.container-env Environment variables that are passed to the container. Environment variable: QUARKUS_SOLACE_DEVSERVICES_CONTAINER_ENV	Map<String,String>
quarkus.solace Any extra parameters to pass to the Solace client. Refer to AuthenticationProperties and TransportLayerProperties for more configuration options Example: To configure compression quarkus.solace.transport.compression-level Environment variable: QUARKUS_SOLACE	Map<String,String>