-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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.
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
Improve GCS docs for using keystore #40605
Conversation
This commit tweaks the wording on using the keystore to store GCS credentials to note it requires a different key type/command. closes elastic#39993
Pinging @elastic/es-distributed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@@ -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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking, but we can use the {es}
attribute instead of Elasticsearch
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what the {es}
attribute is. Can you suggest a specific change to the text?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{es}
here will expand to Elasticsearch
.
To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[Elasticsearch keystore]. You must | |
To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[{es} keystore]. You must |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to skip this for now, as there are other uses of "Elasticsearch" in this file and I don't want to create an inconsistency.
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 tweaks the wording on using the keystore to store GCS credentials to note it requires a different key type/command. closes #39993
…leniency * elastic/master: SQL: Fix deserialisation issue of TimeProcessor (elastic#40776) Improve GCS docs for using keystore (elastic#40605) Add Restore Operation to SnapshotResiliencyTests (elastic#40634) Small refactorings to analysis components (elastic#40745) SQL: Fix display size for DATE/DATETIME (elastic#40669) add HLRC protocol tests for transform state and stats (elastic#40766) Inline TransportReplAction#registerRequestHandlers (elastic#40762) remove experimental label from search_as_you_type documentation (elastic#40744) Remove some abstractions from `TransportReplicationAction` (elastic#40706) Upgrade to latest build scan plugin (elastic#40702) Use default memory lock setting in testing (elastic#40730) Add Bulk Delete Api to BlobStore (elastic#40322) Remove yaml skips older than 7.0 (elastic#40183) Docs: Move id in the java-api (elastic#40748)
This commit tweaks the wording on using the keystore to store GCS credentials to note it requires a different key type/command. closes elastic#39993
This commit tweaks the wording on using the keystore to store GCS
credentials to note it requires a different key type/command.
closes #39993