Configuration Providers

This extension includes two built-in providers that read flag values from Quarkus configuration. These are useful for development, testing, or simple deployments where flags are known at build time or runtime. For production use with dynamic flag evaluation, consider a dedicated provider such as flagd or Unleash.

Runtime configuration provider

The runtime configuration provider reads flag values from Quarkus runtime configuration. Values can be overridden at deploy time using environment variables, system properties, or external config files, as described in Quarkus Configuration documentation.

Add the dependency:

<dependency>
    <groupId>io.quarkiverse.openfeature</groupId>
    <artifactId>quarkus-openfeature-runtime-config</artifactId>
    <version>1.0.0.Alpha1</version>
</dependency>

Define flags in application.properties:

quarkus.openfeature.runtime.new-feature=true
quarkus.openfeature.runtime.greeting=hello
quarkus.openfeature.runtime.max-retries=3
quarkus.openfeature.runtime.threshold=0.75

Values are stored as strings and converted to the requested type at evaluation time. Boolean evaluation never fails because a value cannot be parsed, but note that only true is truthy, all other values are false. Integer and double evaluation throw an error if the value cannot be parsed.

For named domains, flags are scoped under the domain name:

quarkus.openfeature."experimentation".runtime.experiment-a=true
quarkus.openfeature."experimentation".runtime.experiment-b=false

Build-time configuration provider

The build-time configuration provider reads flag values that are fixed at build time. These values are baked into the application and cannot be changed at runtime, even with environment variables or system properties.

Add the dependency:

<dependency>
    <groupId>io.quarkiverse.openfeature</groupId>
    <artifactId>quarkus-openfeature-buildtime-config</artifactId>
    <version>1.0.0.Alpha1</version>
</dependency>

Define flags in application.properties:

quarkus.openfeature.buildtime.stable-feature=true
quarkus.openfeature.buildtime.api-version=v2

For named domains:

quarkus.openfeature."experimentation".buildtime.locked-flag=false

Using both providers

You can use both providers together. Add both dependencies and configure the provider order:

quarkus.openfeature.provider=runtime-config,buildtime-config

The first provider in the list that has a value for a given flag wins. In this example, runtime flags take precedence over build-time flags.

This can be useful to define build-time defaults that are overridable at runtime:

quarkus.openfeature.provider=runtime-config,buildtime-config

# Build-time default
quarkus.openfeature.buildtime.new-feature=false

# Runtime override (e.g., set via environment variable in production)
quarkus.openfeature.runtime.new-feature=true

Configuration Reference

Runtime configuration provider

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

Configuration property

Type

Default

quarkus.openfeature.runtime."flag-name"

quarkus.openfeature."domain-name".runtime."flag-name"

Flag values configurable at runtime, keyed by flag name.

Environment variable: QUARKUS_OPENFEATURE_RUNTIME__FLAG_NAME_

Map<String,String>

Build-time configuration provider

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

Configuration property

Type

Default

quarkus.openfeature.buildtime."flag-name"

quarkus.openfeature."domain-name".buildtime."flag-name"

Flag values fixed at build time, keyed by flag name.

Environment variable: QUARKUS_OPENFEATURE_BUILDTIME__FLAG_NAME_

Map<String,String>