From d518e5ab5118374f6a4b08ba3858efab51e544c8 Mon Sep 17 00:00:00 2001 From: Ryan Ernst Date: Thu, 28 Mar 2019 11:40:04 -0700 Subject: [PATCH] Improve GCS docs for using keystore This commit tweaks the wording on using the keystore to store GCS credentials to note it requires a different key type/command. closes #39993 --- docs/plugins/repository-gcs.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/plugins/repository-gcs.asciidoc b/docs/plugins/repository-gcs.asciidoc index f655d29307074..c1421af548678 100644 --- a/docs/plugins/repository-gcs.asciidoc +++ b/docs/plugins/repository-gcs.asciidoc @@ -88,8 +88,9 @@ A JSON service account file looks like this: ---- // NOTCONSOLE -To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[Elasticsearch keystore]. You must add a setting name of the form `gcs.client.NAME.credentials_file`, where `NAME` -is the name of the client configuration for the repository. The implicit client +To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[Elasticsearch keystore]. You must +add a `file` setting with the name `gcs.client.NAME.credentials_file` using the `add-file` subcommand. + `NAME` is the name of the client configuration for the repository. The implicit client name is `default`, but a different client name can be specified in the repository settings with the `client` key.