Acme Company © Configuration Provider
The acme-configuration extension provides easy integration with our internal conference referential |
Installation
If you want to use this extension, you need to add the io.quarkiverse.approximationcorrector:quarkus-approximation-corrector
extension first to your build file.
For instance, with Maven, directly add the following dependency to your POM file:
<dependency>
<groupId>org.acmer</groupId>
<artifactId>configuration-provider</artifactId>
<version>0</version>
</dependency>
Using command line :
./mvnw quarkus:add-extension -Dextensions='org.acme:configuration-provider'
Or even using the quarkus cli :
quarkus extension add 'org.acme:configuration-provider'
Usage
Simply get values injected through the @ConfigProperty
annotation :
import org.eclipse.microprofile.config.inject.ConfigProperty;
public class FooBar {
@ConfigProperty(name = "acme.property.key") (1)
String value;
}
1 | : All configuration property starting with acme. will be populated. |
Extension Configuration Reference
Configuration property fixed at build time - All other configuration properties are overridable at runtime
Configuration property |
Type |
Default |
||
---|---|---|---|---|
Enable or disable Dev Services explicitly. Dev Services are automatically enabled unless Environment variable: |
boolean |
|
||
The Acme configuration value provider container image to use. <p> Details about default image on Docker Repository on Quay Environment variable: |
string |
|
||
Should the extension be strict when correcting response headers.
Environment variable: |
boolean |
|
||
Should the extension be strict when correcting utils classes.
Environment variable: |
boolean |
|
||
The environment provider server URL.
Environment variable: |
required |