From d26130cb09f96f5a48841e37d5d210e8a8cd0c7b Mon Sep 17 00:00:00 2001 From: Alexander Schwartz Date: Tue, 17 Oct 2023 10:41:44 +0200 Subject: [PATCH] Tidy up documentation around Windows/Linux usage Closes #23856 (cherry picked from commit a3c29b88804547a5f85d60d26b99e23c1f2d0777) --- docs/documentation/server_admin/topics/vault.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/server_admin/topics/vault.adoc b/docs/documentation/server_admin/topics/vault.adoc index 2a0b0fccc44..6206d6f2081 100644 --- a/docs/documentation/server_admin/topics/vault.adoc +++ b/docs/documentation/server_admin/topics/vault.adoc @@ -32,7 +32,7 @@ All built-in providers support the configuration of key resolvers. A key resolve [source,bash] ---- -kc.[sh.bat] start --spi-vault-file-key-resolvers=REALM_UNDERSCORE_KEY,KEY_ONLY +kc.[sh|bat] start --spi-vault-file-key-resolvers=REALM_UNDERSCORE_KEY,KEY_ONLY ---- The resolvers run in the same order you declare them in the configuration. For each resolver, {project_name} uses the last entry name the resolver produces, which combines the realm with the vault key to search for the vault's secret. If {project_name} finds a secret, it returns the secret. If not, {project_name} uses the next resolver. This search continues until {project_name} finds a non-empty secret or runs out of resolvers. If {project_name} finds no secret, {project_name} returns an empty secret.