libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

update/fix-typo-confFileValue-should-be-keystoreValue

Browse source 
- "confFileValue" appears twice consecutively in the same paragraph; the second occurrence should be "keystoreValue".

Thanks to Justin P for pointing that out in [1].

[1] https://github.com/keycloak/keycloak/discussions/33292

Signed-off-by: Pedro Aguiar <contact@codespearhead.com>
This commit is contained in:
Pedro Aguiar 2024-10-02 11:45:36 -04:00 committed by Marek Posolda
parent 7a886aab64
commit 002560ef3e
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/server/configuration.adoc
View file

@ -41,7 +41,7 @@ The following example shows how the `db-url` value is set in four configuration
Based on the priority of application, the value that is used at startup is `cliValue`, because the command line is the highest priority. Based on the priority of application, the value that is used at startup is `cliValue`, because the command line is the highest priority.
If `--db-url=cliValue` had not been used, the applied value would be `KC_DB_URL=envVarValue`. If the value were not applied by either the command line or an environment variable, `db-url=confFileValue` would be used. If none of the previous values were applied, the value `kc.db-url=confFileValue` would be used due to the lowest priority among the available configuration sources. If `--db-url=cliValue` had not been used, the applied value would be `KC_DB_URL=envVarValue`. If the value were not applied by either the command line or an environment variable, `db-url=confFileValue` would be used. If none of the previous values were applied, the value `kc.db-url=keystoreValue` would be used due to the lowest priority among the available configuration sources.
== Formats for configuration == Formats for configuration
The configuration uses a _unified-per-source_ format, which simplifies translation of a key/value pair from one configuration source to another. Note that these formats apply to spi options as well. The configuration uses a _unified-per-source_ format, which simplifies translation of a key/value pair from one configuration source to another. Note that these formats apply to spi options as well.