Improve GCS docs for using keystore (#40605)

This commit tweaks the wording on using the keystore to store GCS
credentials to note it requires a different key type/command.

closes #39993
This commit is contained in:
Ryan Ernst 2019-04-03 07:21:13 -07:00
parent 09ba3ec677
commit b9c46d1dfc
1 changed files with 3 additions and 2 deletions

View File

@ -88,8 +88,9 @@ A JSON service account file looks like this:
---- ----
// NOTCONSOLE // 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` To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[Elasticsearch keystore]. You must
is the name of the client configuration for the repository. The implicit client 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 name is `default`, but a different client name can be specified in the
repository settings with the `client` key. repository settings with the `client` key.