Skip to content

Clarify unsupported secure settings behavior #43454

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.

Sign up for GitHub

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

Merged
rjernst merged 2 commits into from
Jun 20, 2019
Merged

Clarify unsupported secure settings behavior #43454

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
20bf342
Clarify unsupported secure settings behavior
rjernst Jun 20, 2019
60ae559
Update docs/reference/setup/secure-settings.asciidoc
rjernst Jun 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/reference/setup/secure-settings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,12 @@ keystore and the `elasticsearch-keystore` tool to manage the settings in the key

NOTE: All commands here should be run as the user which will run Elasticsearch.

NOTE: Only some settings are designed to be read from the keystore. See
documentation for each setting to see if it is supported as part of the keystore.
IMPORTANT: Only some settings are designed to be read from the keystore. However,
the keystore has no validation to block unsupported settings.
Adding unsupported settings to the keystore will cause {es}
Additional unsupported settings being added to the keystore will cause Elasticsearch
to fail to start. See documentation for each setting to see if it is supported
as part of the keystore.

NOTE: All the modifications to the keystore take affect only after restarting
Elasticsearch.
Expand Down