Package io.quarkus.runtime

Interface ConfigConfig

@ConfigMapping(prefix="quarkus") @ConfigRoot(phase=RUN_TIME) @ConfigDocPrefix("quarkus.config") public interface ConfigConfig
Configuration.

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 ConfigUtils.configBuilder(boolean, io.quarkus.runtime.LaunchMode).

  • Method Details

    • profile

      Optional<List<String>> profile()
      A comma separated list of profiles that will be active when Quarkus launches.

    • profileParent

      @WithName("config.profile.parent") Optional<String> 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

      @WithName("config.locations") Optional<List<URI>> locations()
      Additional config locations to be loaded with the Config. The configuration support multiple locations separated by a comma and each must represent a valid URI.

    • mappingValidateUnknown

      @WithName("config.mapping.validate-unknown") Optional<Boolean> mappingValidateUnknown()
      Validates that a @ConfigMapping maps every available configuration name contained in the mapping prefix.

    • logValues

      @WithName("config.log.values") Optional<Boolean> logValues()
      Enable logging of configuration values lookup in DEBUG log level.
      The log of configuration values require the category set to DEBUG in the io.smallrye.config category: quarkus.log.category."io.smallrye.config".level=DEBUG.

    • buildTimeMismatchAtRuntime

      @WithName("config.build-time-mismatch-at-runtime") @WithDefault("warn") ConfigConfig.BuildTimeMismatchAtRuntime buildTimeMismatchAtRuntime()
      What should happen if the application is started with a different build time configuration than it was compiled against. This may be useful to prevent misconfiguration.

      If this is set to warn the application will warn at start up.

      If this is set to fail the application will fail at start up.

      Native tests leveraging@io.quarkus.test.junit.TestProfile are always run with quarkus.config.build-time-mismatch-at-runtime = fail.