From f595f4e05286dc6ba90dac4fb7cecb91035126eb Mon Sep 17 00:00:00 2001 From: Joe Di Pol Date: Wed, 21 Aug 2024 09:43:08 -0700 Subject: [PATCH] Clarify description of config profiles --- docs/mp/config/introduction.adoc | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/mp/config/introduction.adoc b/docs/mp/config/introduction.adoc index 91b9d8434b2..2f560b9b8b8 100644 --- a/docs/mp/config/introduction.adoc +++ b/docs/mp/config/introduction.adoc @@ -127,9 +127,14 @@ server.host=0.0.0.0 ==== {spec-name} Profiles [[Config-Profiles]] {spec-name} supports a concept of configuration profiles. You can define a profile using the configuration property `mp.config.profile` -(when using default configuration, this can be defined as a system property, environment variable or as a property in `microprofile-config.properties`). -When a profile is defined, additional config source is loaded (`microprofile-config-profile.properties`) and properties from profile have precedence over -default properties. Profile properties can be defined using `%profile` prefix, such as `%dev.server.port`. +This can be defined as a system property, environment variable or as a property in `microprofile-config.properties` (when default configuration is used). +When a profile is defined, an additional config source is loaded: `microprofile-config-.properties` and properties in the profile +specific config source will override properties set in the default config source. + +You can also use profiles on a per property level. Profile specific properties are defined using `%` prefix, such as `%dev.server.port`. +This will override the plain property `server.port`. + +For more details see link:{microprofile-config-spec-url}#_how_config_profile_works[How Config Profiles work] === Helidon {spec-name} Features