Chapter 1. Configuring your Red Hat build of Quarkus applications by using a properties file
As an application developer, you can use Red Hat build of Quarkus to create microservices-based applications written in Java that run on OpenShift and serverless environments. Applications compiled to native executables have small memory footprints and fast startup times.
You can configure your Quarkus application by using either of the following methods:
-
Setting properties in the
application.propertiesfile -
Applying structured configuration in YAML format by updating the
application.yamlfile
You can also extend and customize the configuration for your application by doing the following:
- Substituting and composing configuration property values by using property expressions
- Implementing MicroProfile-compliant classes with custom configuration source converters that read configuration values from different external sources
- Using configuration profiles to keep separate sets of configuration values for your development, test, and production environments
The procedures include configuration examples that are created by using the Quarkus config-quickstart exercise.
Prerequisites
You have installed OpenJDK 17 or 21 and set the
JAVA_HOMEenvironment variable to specify the location of the Java SDK.- To download the Red Hat build of OpenJDK, log in to the Red Hat Customer Portal and go to Software Downloads.
You have installed Apache Maven 3.8.6 or later.
- Download Maven from the Apache Maven Project website.
You have configured Maven to use artifacts from the Quarkus Maven repository.
- To learn how to configure Maven settings, see Getting started with Quarkus.
1.1. Red Hat configuration options Copy linkLink copied to clipboard!
You can use configuration options to change the settings of your application in a single configuration file. Red Hat build of Quarkus supports configuration profiles that you can use to group related properties and switch between profiles as required.
By default, Quarkus reads properties from the application.properties file located in the src/main/resources directory. You can also configure Quarkus to read properties from a YAML file instead.
When you add the quarkus-config-yaml dependency to your project pom.xml file, you can configure and manage your application properties in the application.yaml file. For more information, see Adding YAML configuration support.
Red Hat build of Quarkus also supports MicroProfile Config, which you can use to load your application’s configuration from other sources.
You can use the MicroProfile Config specification from the Eclipse MicroProfile project to inject configuration properties into your application and access them by using a method defined in your code.
Quarkus can also read application properties from different origins, including the following sources:
- The file system
- A database
-
A Kubernetes or OpenShift Container Platform
ConfigMapor Secret object - Any source that a Java application can load
1.2. Creating the configuration quickstart project Copy linkLink copied to clipboard!
With the config-quickstart project, you can get up and running with a simple Quarkus application by using Apache Maven and the Quarkus Maven plugin. The following procedure describes how you can create a Quarkus Maven project.
Prerequisites
You have installed OpenJDK 17 or 21 and set the
JAVA_HOMEenvironment variable to specify the location of the Java SDK.- To download Red Hat build of OpenJDK, log in to the Red Hat Customer Portal and go to Software Downloads.
You have installed Apache Maven 3.8.6 or later.
- Download Maven from the Apache Maven Project website.
Procedure
Verify that Maven uses OpenJDK 17 or 21 and that the Maven version is 3.8.6 or later:
mvn --version
mvn --versionCopy to Clipboard Copied! Toggle word wrap Toggle overflow If the
mvncommand does not return OpenJDK 17 or 21, ensure that the directory where OpenJDK 17 or 21 is installed on your system is included in thePATHenvironment variable:export PATH=$PATH:<path_to_JDK>
export PATH=$PATH:<path_to_JDK>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the following command to generate the project:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
The preceding mvn command creates the following items in the config-quickstart directory:
- The Maven project directory structure
-
An
org.acme.config.GreetingResourceresource -
A landing page that you can access at
http://localhost:8080after you start the application - Associated unit tests for testing your application in native mode and JVM mode
-
Example
Dockerfile.jvmandDockerfile.nativefiles in thesrc/main/dockersubdirectory - The application configuration file
Alternatively, you can download a Quarkus Maven project to use in this tutorial from the Quarkus Quickstarts archive or clone the Quarkus Quickstarts Git repository. The Quarkus config-quickstart exercise is located in the config-quickstart directory.
1.3. Injecting configuration values into your Red Hat build of Quarkus application Copy linkLink copied to clipboard!
Red Hat build of Quarkus uses the MicroProfile Config feature to inject configuration data into the application. You can access the configuration by using context and dependency injection (CDI) or by defining a method in your code.
Use the @ConfigProperty annotation to map an object property to a key in the MicroProfile Config Sources file of your application.
The following procedure and examples show how you can inject an individual property configuration into a Quarkus config-quickstart project by using the Red Hat build of Quarkus Application configuration file, application.properties.
You can use a MicroProfile Config configuration file, src/main/resources/META-INF/microprofile-config.properties, in exactly the same way you use the application.properties file.
Using the application.properties file is the preferred method.
Prerequisites
You have created the Quarkus config-quickstart project.
Procedure
-
Open the
src/main/resources/application.propertiesfile. Add configuration properties to your configuration file where
<property_name>is the property name and<value>is the value of the property:<property_name>=<value>
<property_name>=<value>Copy to Clipboard Copied! Toggle word wrap Toggle overflow The following example shows how to set the values for the
greeting.messageand thegreeting.nameproperties in the Quarkusconfig-quickstartproject:Example
application.propertiesfilegreeting.message=hello greeting.name=quarkus
greeting.message=hello greeting.name=quarkusCopy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantWhen you are configuring your applications, do not prefix application-specific properties with the string
quarkus. Thequarkusprefix is reserved for configuring Quarkus at the framework level. Usingquarkusas a prefix for application-specific properties might lead to unexpected results when your application runs.Review the
GreetingResource.javaJava file in your project. The file contains theGreetingResourceclass with thehello()method that returns a message when you send an HTTP request on the/greetingendpoint:Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow In the example provided, the values of the
messageandnamestrings in thehello()method are not initialized. The application throws aNullPointerExceptionwhen the endpoint is called and starts successfully in this state.Define the
message,name, andsuffixfields, and annotate them with@ConfigProperty, matching the values that you defined for thegreeting.messageandgreeting.nameproperties. Use the@ConfigPropertyannotation to inject the configuration value for each string. For example:Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- If you do not configure a value for the
greeting.messagestring, the application fails and throws the following exception:jakarta.enterprise.inject.spi.DeploymentException: io.quarkus.runtime.configuration.ConfigurationException: Failed to load config value of type class java.lang.String for: greeting.message - 2
- If you do not configure a value for the
greeting.suffix, Quarkus resolves it to the default value. - 3
- If you do not define the
greeting.nameproperty, the value ofnameis not available. Your application still runs even when this value is not available because you set theOptionalparameter onname.
NoteTo inject a configured value, you can use
@ConfigProperty. You do not need to include the@Injectannotation for members that you annotate with@ConfigProperty.
Compile and start your application in development mode:
./mvnw quarkus:dev
./mvnw quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the following command in a new terminal window to verify that the endpoint returns the message:
curl http://localhost:8080/greeting
curl http://localhost:8080/greetingCopy to Clipboard Copied! Toggle word wrap Toggle overflow This command returns the following output:
hello quarkus!
hello quarkus!Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To stop the application, press Ctrl+C.
1.4. Updating the functional test to validate configuration changes Copy linkLink copied to clipboard!
Before you test the functionality of your application, you must update the functional test to reflect the changes that you made to the endpoint of your application. The following procedure shows how you can update your testHelloEndpoint method on the Quarkus config-quickstart project.
Procedure
-
Open the
GreetingResourceTest.javafile. Update the content of the
testHelloEndpointmethod:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.5. Setting configuration properties Copy linkLink copied to clipboard!
By default, Quarkus reads properties from the application.properties file that is in the src/main/resources directory. If you change build properties, ensure that you repackage your application.
Quarkus configures most properties during build time. Extensions can define properties as overridable at runtime, for example, the database URL, a user name, and a password, which can be specific to your target environment.
Prerequisites
-
You have created the Quarkus
config-quickstartproject. -
You have defined the
greeting.messageandgreeting.nameproperties in theapplication.propertiesfile of your project.
Procedure
To package your Quarkus project, enter the following command:
./mvnw clean package
./mvnw clean packageCopy to Clipboard Copied! Toggle word wrap Toggle overflow Use one of the following methods to set the configuration properties:
Setting system properties:
Enter the following command, where
<property_name>is the name of the configuration property that you want to add and<value>is the value of the property:java -D<property_name>=<value> -jar target/quarkus-app/quarkus-run.jar
java -D<property_name>=<value> -jar target/quarkus-app/quarkus-run.jarCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to set the value of the
quarkus.datasource.passwordproperty, enter the following command:java -Dgreeting.suffix=? -jar target/quarkus-app/quarkus-run.jar
java -Dgreeting.suffix=? -jar target/quarkus-app/quarkus-run.jarCopy to Clipboard Copied! Toggle word wrap Toggle overflow Setting environment variables:
Enter the following command, where
<property_name>is the name of the configuration property that you want to set and<value>is the value of the property:export <property_name>=<value> ; java -jar target/quarkus-app/quarkus-run.jar
export <property_name>=<value> ; java -jar target/quarkus-app/quarkus-run.jarCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteEnvironment variable names follow the conversion rules of Eclipse MicroProfile. Convert the name to upper case and replace any character that is not alphanumeric with an underscore (
_).Using an environment file:
Create a
.envfile in your current working directory and add configuration properties, where<PROPERTY_NAME>is the property name and<value>is the value of the property:<PROPERTY_NAME>=<value>
<PROPERTY_NAME>=<value>Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteIn development mode, this file is in the root directory of your project. Do not track the file in version control. If you create a
.envfile in the root directory of your project, you can define keys and values that the program reads as properties.Using the
application.propertiesfile:Place the configuration file in the
$PWD/config/application.propertiesdirectory where the application runs so that any runtime properties that are defined in that file override the default configuration.NoteYou can also use the
config/application.propertiesfeatures in development mode. Place theconfig/application.propertiesfile inside thetargetdirectory. Any cleaning operation from the build tool, for example,mvn clean, also removes theconfigdirectory.
1.6. Advanced configuration mapping Copy linkLink copied to clipboard!
The following advanced mapping procedures are extensions that are specific to Red Hat build of Quarkus and are outside of the MicroProfile Config specification.
1.6.1. Annotating an interface with @ConfigMapping Copy linkLink copied to clipboard!
Instead of individually injecting multiple related configuration values, use the @io.smallrye.config.ConfigMapping annotation to group configuration properties. The following procedure describes how you can use the @ConfigMapping annotation on the Quarkus config-quickstart project.
Prerequisites
-
You have created the Quarkus
config-quickstartproject. -
You have defined the
greeting.messageandgreeting.nameproperties in theapplication.propertiesfile of your project.
Procedure
Review the
GreetingResource.javafile in your project and ensure that it contains the contents that are shown in the following example. To use the@ConfigPopertiesannotation to inject configuration properties from another configuration source into this class, you must import thejava.util.Optionalandorg.eclipse.microprofile.config.inject.ConfigPropertypackages.Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a
GreetingConfiguration.javafile in thesrc/main/java/org/acme/configdirectory. Add the import statements forConfigMappingandOptionalto the file:Example
GreetingConfiguration.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Inject the
GreetingConfigurationinstance into theGreetingResourceclass by using the@Injectannotation, as follows:NoteThis snippet replaces the three fields that are annotated with
@ConfigPropertythat are in the initial version of theconfig-quickstartproject.Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Compile and start your application in development mode:
./mvnw quarkus:dev
./mvnw quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantIf you do not give values for the class properties, the application fails to compile, and an
io.smallrye.config.ConfigValidationExceptionerror is returned to indicate that a value is missing. This does not apply to optional fields or fields with a default value.To verify that the endpoint returns the message, enter the following command in a new terminal window:
curl http://localhost:8080/greeting
curl http://localhost:8080/greetingCopy to Clipboard Copied! Toggle word wrap Toggle overflow You receive the following message:
hello quarkus!
hello quarkus!Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To stop the application, press Ctrl+C.
1.6.2. Using nested object configuration Copy linkLink copied to clipboard!
You can define an interface that is nested inside another interface. This procedure shows how to create and configure a nested interface in the Quarkus config-quickstart project.
Prerequisites
-
You have created the Quarkus
config-quickstartproject. -
You have defined the
greeting.messageandgreeting.nameproperties in theapplication.propertiesfile of your project.
Procedure
Review the
GreetingResource.javain your project. The file contains theGreetingResourceclass with thehello()method that returns a message when you send an HTTP request on the/greetingendpoint:Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a
GreetingConfiguration.javaclass file with theGreetingConfigurationinstance. This class contains the externalized configuration for thehello()method that is defined in theGreetingResourceclass:Example
GreetingConfiguration.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create the
ContentConfiginterface that is nested inside theGreetingConfigurationinstance, as shown in the following example:Example
GreetingConfiguration.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThe method name of the
ContentConfiginterface iscontent. To ensure that you bind the properties to the correct interface, when you define configuration properties for this class, usecontentin the prefix. In doing so, you can also prevent property name conflicts and unexpected application behavior.Define the
greeting.content.prize-amountandgreeting.content.recipientsconfiguration properties in yourapplication.propertiesfile.The following example shows the properties defined for the
GreetingConfigurationinstance and theContentConfiginterface:Example
application.propertiesfilegreeting.message=hello greeting.name=quarkus greeting.content.prize-amount=10 greeting.content.recipients=Jane,John
greeting.message=hello greeting.name=quarkus greeting.content.prize-amount=10 greeting.content.recipients=Jane,JohnCopy to Clipboard Copied! Toggle word wrap Toggle overflow Instead of the three
@ConfigPropertyfield annotations, inject theGreetingConfigurationinstance into theGreetingResourceclass by using the@Injectannotation, as outlined in the following example. Also, you must update the message string that the/greetingendpoint returns with the values that you set for the newgreeting.content.prize-amountandgreeting.content.recipientsproperties that you added.Example
GreetingResource.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Compile and start your application in development mode:
./mvnw quarkus:dev
./mvnw quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantIf you do not provide values for the class properties, the application fails to compile and you receive a
jakarta.enterprise.inject.spi.DeploymentExceptionexception that indicates a missing value. This does not apply toOptionalfields and fields with a default value.To verify that the endpoint returns the message, open a new terminal window and enter the following command:
curl http://localhost:8080/greeting
curl http://localhost:8080/greetingCopy to Clipboard Copied! Toggle word wrap Toggle overflow A message displays, containing two lines of output. The first line displays the greeting, and the second line reports the recipients of the prize together with the prize amount, as follows:
hello quarkus! Jane,John receive total of candies: 10
hello quarkus! Jane,John receive total of candies: 10Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To stop the application, press Ctrl+C.
You can annotate classes that are annotated with @ConfigMapping with bean validation annotations similar to the following example:
Your project must include the quarkus-hibernate-validator dependency.
1.7. Accessing the configuration programmatically Copy linkLink copied to clipboard!
You can define a method in your code to retrieve the values of the configuration properties in your application. In doing so, you can dynamically look up configuration property values or retrieve configuration property values from classes that are either CDI beans or Jakarta REST (formerly known as JAX-RS) resources.
You can access the configuration by using the org.eclipse.microprofile.config.ConfigProvider.getConfig() method. The getValue() method of the config object returns the values of the configuration properties.
Prerequisites
- You have a Quarkus Maven project.
Procedure
Use a method to access the value of a configuration property of any class or object in your application code. Depending on whether or not the value that you want to retrieve is set in a configuration source in your project, you can use one of the following methods:
To access the value of a property that is set in a configuration source in your project, for example, in the
application.propertiesfile, use thegetValue()method:String <variable-name> = ConfigProvider.getConfig().getValue("<property-name>", <data-type-class-name>.class);String <variable-name> = ConfigProvider.getConfig().getValue("<property-name>", <data-type-class-name>.class);Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to retrieve the value of the
greeting.messageproperty that has the data typeString, and is assigned to themessagevariable in your code, use the following syntax:String message = ConfigProvider.getConfig().getValue("greeting.message",String.class);String message = ConfigProvider.getConfig().getValue("greeting.message",String.class);Copy to Clipboard Copied! Toggle word wrap Toggle overflow When you want to retrieve a value that is optional or default and might not be defined in your
application.propertiesfile or another configuration source in your application, use thegetOptionalValue()method:Optional_<String>_ <variable-name> = ConfigProvider.getConfig().getOptionalValue("<property-name>", <data-type-class-name>.class);Optional_<String>_ <variable-name> = ConfigProvider.getConfig().getOptionalValue("<property-name>", <data-type-class-name>.class);Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to retrieve the value of the
greeting.nameproperty that is optional, has the data typeString, and is assigned to thenamevariable in your code, use the following syntax:Optional_<String>_ name = ConfigProvider.getConfig().getOptionalValue("greeting.name", String.class);Optional_<String>_ name = ConfigProvider.getConfig().getOptionalValue("greeting.name", String.class);Copy to Clipboard Copied! Toggle word wrap Toggle overflow
The following snippet shows a variant of the aforementioned GreetingResource class by using the programmatic access to the configuration:
src/main/java/org/acme/config/GreetingResource.java
1.8. Property expressions Copy linkLink copied to clipboard!
You can combine property references and text strings into property expressions and use these expressions as values in your Quarkus configuration.
Like variables, property expressions substitute configuration property values dynamically, avoiding hard-coded values.
You can expand an expression in one configuration source with a value defined in another.
The application resolves a property expression when java.util.Properties reads the property value from a configuration source: at compile time if read then, and at runtime if overridden at that point.
If the application cannot resolve the value of a property in an expression, and the property does not have a default value, your application throws a NoSuchElementException error.
1.8.1. Example usage of property expressions Copy linkLink copied to clipboard!
To achieve flexibility when you configure your Quarkus application, you can use property expressions as shown in the following examples.
Substituting the value of a configuration property:
To avoid hardcoding property values in your configuration, you can use a property expression. Use the
${<property_name>}syntax to write an expression that references a configuration property, as shown in the following example:Example
application.propertiesfileremote.host=quarkus.io callable.url=https://${remote.host}/remote.host=quarkus.io callable.url=https://${remote.host}/Copy to Clipboard Copied! Toggle word wrap Toggle overflow The value of the
callable.urlproperty resolves tohttps://quarkus.io/.Setting a property value that is specific to a particular configuration profile:
In the following example, the
%devconfiguration profile and the default configuration profile are set to use data source connection URLs with different host addresses.Example
application.propertiesfile%dev.quarkus.datasource.jdbc.url=jdbc:mysql://localhost:3306/mydatabase?useSSL=false quarkus.datasource.jdbc.url=jdbc:mysql://remotehost:3306/mydatabase?useSSL=false
%dev.quarkus.datasource.jdbc.url=jdbc:mysql://localhost:3306/mydatabase?useSSL=false quarkus.datasource.jdbc.url=jdbc:mysql://remotehost:3306/mydatabase?useSSL=falseCopy to Clipboard Copied! Toggle word wrap Toggle overflow Depending on the configuration profile used to start your application, your data source driver uses the database URL that you set for the profile.
You can achieve the same result in a simplified way by setting a different value for the custom
application.serverproperty for each configuration profile. Then, you can reference the property in the database connection URL of your application, as shown in the following example:Example
application.propertiesfile%dev.application.server=localhost application.server=remotehost quarkus.datasource.jdbc.url=jdbc:mysql://${application.server}:3306/mydatabase?useSSL=false%dev.application.server=localhost application.server=remotehost quarkus.datasource.jdbc.url=jdbc:mysql://${application.server}:3306/mydatabase?useSSL=falseCopy to Clipboard Copied! Toggle word wrap Toggle overflow The
application.serverproperty resolves to the appropriate value depending on the profile that you choose when you run your application.Setting a default value of a property expression:
You can define a default value for a property expression. Quarkus uses the default value if the value of the property that is required to expand the expression is not resolved from any of your configuration sources. You can set a default value for an expression by using the following syntax:
${<property_name>:<default_value>}${<property_name>:<default_value>}Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the following example, the property expression in the data source URL uses
mysql.db.serveras the default value of theapplication.serverproperty:Example
application.propertiesfilequarkus.datasource.jdbc.url=jdbc:mysql://${application.server:mysql.db.server}:3306/mydatabase?useSSL=falsequarkus.datasource.jdbc.url=jdbc:mysql://${application.server:mysql.db.server}:3306/mydatabase?useSSL=falseCopy to Clipboard Copied! Toggle word wrap Toggle overflow Nesting property expressions:
You can compose property expressions by nesting a property expression inside another property expression. When nested property expressions are expanded, the inner expression is expanded first. You can use the following syntax for nesting property expressions:
${<outer_property_name>${<inner_property_name>}}${<outer_property_name>${<inner_property_name>}}Copy to Clipboard Copied! Toggle word wrap Toggle overflow Combining multiple property expressions:
You can join two or more property expressions together by using the following syntax:
${<first_property_name>}${<second_property_name>}${<first_property_name>}${<second_property_name>}Copy to Clipboard Copied! Toggle word wrap Toggle overflow Combining property expressions with environment variables:
You can use property expressions to substitute the values of environment variables. The expression in the following example substitutes the value that is set for the
HOSTenvironment variable as the value of theapplication.hostproperty:Example
application.propertiesfileremote.host=quarkus.io application.host=${HOST:${remote.host}}remote.host=quarkus.io application.host=${HOST:${remote.host}}Copy to Clipboard Copied! Toggle word wrap Toggle overflow
When the HOST environment variable is not set, the application.host property uses the value of the remote.host property as the default.
1.9. Using configuration profiles Copy linkLink copied to clipboard!
You can use different configuration profiles depending on your environment. With configuration profiles, you can have multiple configurations in the same file and to select between them by using a profile name.
Red Hat build of Quarkus has the following three default configuration profiles:
- dev: Activated in development mode
- test: Activated when running tests
- prod: The default profile when not running in development or test mode
In addition, you can create your own custom profiles.
Prerequisites
You have a Quarkus Maven project.
Procedure
Open your Java resource file and add the following import statement:
import io.quarkus.runtime.configuration.ConfigUtils;
import io.quarkus.runtime.configuration.ConfigUtils;Copy to Clipboard Copied! Toggle word wrap Toggle overflow To get a List of the current profiles, add a log by invoking the
ConfigUtils.getProfiles()method:LOGGER.infof("The application is starting with profiles `%s`", ConfigUtils.getProfiles());LOGGER.infof("The application is starting with profiles `%s`", ConfigUtils.getProfiles());Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.9.1. Setting a custom configuration profile Copy linkLink copied to clipboard!
You can create as many configuration profiles as you want. You can have multiple configurations in the same file and you can select a configuration by using a profile name.
Procedure
To set a custom profile, create a configuration property with the profile name in the
application.propertiesfile, where<property_name>is the name of the property,<value>is the property value, and<profile>is the name of a profile:Create a configuration property
%<profile>.<property_name>=<value>
%<profile>.<property_name>=<value>Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the following example configuration, the value of
quarkus.http.portis9090by default, and becomes8181when thedevprofile is activated:Example configuration
quarkus.http.port=9090 %dev.quarkus.http.port=8181
quarkus.http.port=9090 %dev.quarkus.http.port=8181Copy to Clipboard Copied! Toggle word wrap Toggle overflow Use one of the following methods to enable a profile:
Set the
quarkus.profilesystem property.To enable a profile by using the
quarkus.profilesystem property, enter the following command:Enable a profile by using
quarkus.profilepropertymvn -Dquarkus.profile=<value> quarkus:dev
mvn -Dquarkus.profile=<value> quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Set the
QUARKUS_PROFILEenvironment variable.To enable profile by using an environment variable, enter the following command:
Enable a profile by using an environment variable
export QUARKUS_PROFILE=<profile>
export QUARKUS_PROFILE=<profile>Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThe system property value takes precedence over the environment variable value.
To repackage the application and change the profile, enter the following command:
Change a profile
./mvnw package -Dquarkus.profile=<profile> java -jar target/quarkus-app/quarkus-run.jar
./mvnw package -Dquarkus.profile=<profile> java -jar target/quarkus-app/quarkus-run.jarCopy to Clipboard Copied! Toggle word wrap Toggle overflow The following example shows a command that activates the
prod-awsprofile:Example command to activate a profile
./mvnw package -Dquarkus.profile=prod-aws java -jar target/quarkus-app/quarkus-run.jar
./mvnw package -Dquarkus.profile=prod-aws java -jar target/quarkus-app/quarkus-run.jarCopy to Clipboard Copied! Toggle word wrap Toggle overflow
The default Quarkus application runtime profile is set to the profile that is used to build the application. Red Hat build of Quarkus automatically selects a profile depending on your environment mode. For example, when your application is running as a JAR, Quarkus is in prod mode.
1.10. Setting custom configuration sources Copy linkLink copied to clipboard!
By default, a Quarkus application reads properties from the application.properties file in the src/main/resources subdirectory of your project. With Quarkus, you can load application configuration properties from other sources according to the MicroProfile Config specification for externalized configuration. You can enable your application to load configuration properties from other sources by defining classes that implement the org.eclipse.microprofile.config.spi.ConfigSource and the org.eclipse.microprofile.config.spi.ConfigSourceProvider interfaces. This procedure demonstrates how you can implement a custom configuration source in your Quarkus project.
Prerequisite
You have the Quarkus config-quickstart project.
Procedure
Create a class file in your project that implements the
org.eclipse.microprofile.config.spi.ConfigSourceProviderinterface. To return a list ofConfigSourceobjects, you must override thegetConfigSources()method.Example
org.acme.config.InMemoryConfigSourceProviderCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create the
InMemoryConfigSourceclass that implements theorg.eclipse.microprofile.config.spi.ConfigSourceinterface:Example
org.acme.config.InMemoryConfigSourceCopy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- The
getOrdinal()method returns the priority of theConfigSourceclass. Therefore, when multiple configuration sources define the same property, Quarkus can select the appropriate value as defined by theConfigSourceclass with the highest priority.
In the
src/main/resources/META-INF/services/subdirectory of your project, create a file namedorg.eclipse.microprofile.config.spi.ConfigSourceProviderand enter the fully-qualified name of the class that implements theConfigSourceProviderin the file that you created:Example
org.eclipse.microprofile.config.spi.ConfigSourceProviderfile:org.acme.config.InMemoryConfigSourceProvider
org.acme.config.InMemoryConfigSourceProviderCopy to Clipboard Copied! Toggle word wrap Toggle overflow To ensure that the
ConfigSourceProviderthat you created is registered and installed when you compile and start your application, you must complete the previous step.Edit the
GreetingResource.javafile in your project to add the following update:@ConfigProperty(name="my.prop") int value;
@ConfigProperty(name="my.prop") int value;Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the
GreetingResource.javafile, extend thehellomethod to use the new property:@GET @Produces(MediaType.TEXT_PLAIN) public String hello() { return message + " " + name.orElse("world") + " " + value; }@GET @Produces(MediaType.TEXT_PLAIN) public String hello() { return message + " " + name.orElse("world") + " " + value; }Copy to Clipboard Copied! Toggle word wrap Toggle overflow To compile and start your application in development mode, enter the following command:
./mvnw quarkus:dev
./mvnw quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow To verify that the
/greetingendpoint returns the expected message, open a terminal window and enter the following command:Example request
curl http://localhost:8080/greeting
curl http://localhost:8080/greetingCopy to Clipboard Copied! Toggle word wrap Toggle overflow When your application successfully reads the custom configuration, the command returns the following response:
hello world 1234
hello world 1234Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.11. Using custom configuration converters as configuration values Copy linkLink copied to clipboard!
You can store custom types as configuration values by implementing org.eclipse.microprofile.config.spi.Converter<T> and adding its fully qualified class name into the META-INF/services/org.eclipse.microprofile.config.spi.Converter file. By using converters, you can transform the string representation of a value into an object.
Prerequisites
You have created the Quarkus config-quickstart project.
Procedure
In the
org.acme.configpackage, create theorg.acme.config.MyCustomValueclass with the following content:Example of custom configuration value
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Implement the converter class to override the convert method to produce a
MyCustomValueinstance.Example implementation of converter class
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Add the fully-qualified class name of the converter,
org.acme.config.MyCustomValueConverter, to yourMETA-INF/services/org.eclipse.microprofile.config.spi.Converterservice file. In the
GreetingResource.javafile, inject theMyCustomValueproperty:@ConfigProperty(name="custom") MyCustomValue value;
@ConfigProperty(name="custom") MyCustomValue value;Copy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
hellomethod to use this value:@GET @Produces(MediaType.TEXT_PLAIN) public String hello() { return message + " " + name.orElse("world") + " - " + value.value(); }@GET @Produces(MediaType.TEXT_PLAIN) public String hello() { return message + " " + name.orElse("world") + " - " + value.value(); }Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the
application.propertiesfile, add the string representation to be converted:custom=1234
custom=1234Copy to Clipboard Copied! Toggle word wrap Toggle overflow To compile and start your application in development mode, enter the following command:
./mvnw quarkus:dev
./mvnw quarkus:devCopy to Clipboard Copied! Toggle word wrap Toggle overflow To verify that the
/greetingendpoint returns the expected message, open a terminal window and enter the following command:Example request
curl http://localhost:8080/greeting
curl http://localhost:8080/greetingCopy to Clipboard Copied! Toggle word wrap Toggle overflow When your application successfully reads the custom configuration, the command returns the following response:
hello world - 1234
hello world - 1234Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYour custom converter class must be
publicand must have apublicno-argument constructor. Your custom converter class cannot beabstract.
1.11.1. Setting custom converters priority Copy linkLink copied to clipboard!
The default priority for all Quarkus core converters is 200. For all other converters, the default priority is 100. You can increase the priority of your custom converters by using the jakarta.annotation.Priority annotation.
The following procedure demonstrates an implementation of a custom converter, AnotherCustomValueConverter, which has a priority of 150. This takes precedence over MyCustomValueConverter from the previous section, which has a default priority of 100.
Prerequisites
-
You have created the Quarkus
config-quickstartproject. - You have created a custom configuration converter for your application.
Procedure
Set a priority for your custom converter by annotating the class with the
@Priorityannotation and passing it a priority value. In the following example, the priority value is set to150.Example
AnotherCustomValueConverter.javafileCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a file named
org.eclipse.microprofile.config.spi.Converterin thesrc/main/resources/META-INF/services/subdirectory of your project, and enter the fully qualified name of the class that implements theConverterin the file that you created:Example
org.eclipse.microprofile.config.spi.Converterfileorg.acme.config.AnotherCustomValueConverter
org.acme.config.AnotherCustomValueConverterCopy to Clipboard Copied! Toggle word wrap Toggle overflow You must complete the previous step to ensure that the
Converteryou created is registered and installed when you compile and start your application.
Verification
After you complete the required configuration, the next step is to compile and package your Quarkus application. For more information and examples, see the compiling and packaging sections of the Getting started with Quarkus guide.