Package io.quarkus.runtime
Interface ConfigConfig
We don't really use this, because these are configurations for the config itself, so it causes a chicken / egg
problem, but we need it for documentation purposes.
Relocation of the Config configurations to the Quarkus namespace is done in
Relocation of the Config configurations to the Quarkus namespace is done in
ConfigUtils.configBuilder(boolean, io.quarkus.runtime.LaunchMode)
.-
Method Summary
Modifier and TypeMethodDescriptionAdditional config locations to be loaded with the Config.Enable logging of configuration values lookup in DEBUG log level.Validates that a@ConfigMapping
maps every available configuration name contained in the mapping prefix.profile()
A comma separated list of profiles that will be active when Quarkus launches.Accepts a single configuration profile name.uuid()
A property that allows accessing a generated UUID.
-
Method Details
-
profile
A comma separated list of profiles that will be active when Quarkus launches. -
profileParent
Accepts a single configuration profile name. If a configuration property cannot be found in the current active profile, the config performs the same lookup in the profile set by this configuration. -
locations
Additional config locations to be loaded with the Config. The configuration support multiple locations separated by a comma and each must represent a validURI
. -
mappingValidateUnknown
Validates that a@ConfigMapping
maps every available configuration name contained in the mapping prefix. -
logValues
Enable logging of configuration values lookup in DEBUG log level.
The log of configuration values require the category set toDEBUG
in theio.smallrye.config
category:quarkus.log.category."io.smallrye.config".level=DEBUG
. -
uuid
A property that allows accessing a generated UUID. It generates that UUID at startup time. So it changes between two starts including in dev mode.
Access this generated UUID using expressions: `${quarkus.uuid}`.
-