Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.x: Clarify description of config profiles #9188

Merged
merged 1 commit into from
Aug 21, 2024
Merged

4.x: Clarify description of config profiles #9188

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions docs/src/main/asciidoc/mp/config/introduction.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,9 +126,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-<profile_name>.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 `%<profile_name>` 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

Expand Down