-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Don't allow secure settings in YML config (109115) #115779
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
Conversation
Elasticsearch should refuse to start if a secure setting is defined in elasticsearch.yml, in order to protect users from accidentally putting their secrets in a place where they are unexpectedly visible Fixes elastic#109115
Hi @alexey-ivanov-es, I've created a changelog YAML for you. |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
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.
Seems straightforward
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.
Hang on, I think this is a breaking change, we need to clear it with the breaking changes committee first and document it as breaking. I suspect we should be emitting warnings in 8.x as well to help folks avoid the problem before it actually takes effect.
@DaveCTurner I discussed this with @rjernst and he said: "I confirmed that we are ok to proceed with the above change. it's an edge case which is in a gray area we shouldn't need an explicit breaking change issue for." |
Ok carry on then. |
* Don't allow secure settings in YML config (109115) Elasticsearch should refuse to start if a secure setting is defined in elasticsearch.yml, in order to protect users from accidentally putting their secrets in a place where they are unexpectedly visible Fixes #109115
Elasticsearch should refuse to start
if a secure setting is defined in elasticsearch.yml, in order to protect users from accidentally putting their secrets in a place where they are unexpectedly visible
Fixes #109115