-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove previously deprecated elasticsearch.*
settings.
#29496
Remove previously deprecated elasticsearch.*
settings.
#29496
Conversation
Pinging @elastic/kibana-platform |
💚 Build Succeeded |
@@ -97,13 +97,6 @@ considered unique based on its persistent UUID, which is written to the path.dat | |||
|
|||
*Impact:* The logging.useUTC flag will have to be replaced with a timezone id. If set to true the id is `UTC`. | |||
|
|||
[float] |
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.
note: I thought it'd make sense to join these two notes into one, let me know if you have a better wording.
@@ -1,97 +0,0 @@ | |||
/* |
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.
note: tests were testing only config deprecations.
Hey @elastic/stack-monitoring, we've recently removed deprecated |
Regarding the monitoring settings, we need to make sure the new (replacement) settings are supported in 6.7 at least (if not earlier) so users have a chance to move over to them first. Then we can remove them in 7.0. Even then, it's rather short notice which is not ideal but it's the least we should do at this point. /cc @chrisronline |
If I'm not mistaken |
Yes @azasypkin that's correct. Can we just update this PR to remove those deprecations and add the steps to the 7.0 migration doc? Or should we do it in another PR? |
These settings are so closely interconnected that I'd do it in this PR (copy-paste basically) unless there are any objections? |
@azasypkin Agreed. Thanks! |
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
💚 Build Succeeded |
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!
This PR:
Removes the ability to use
elasticsearch.url
and requires that the user useselasticsearch.hosts
insteadRemoves the ability to use
elasticsearch.ssl.verify
and requires that the user useselasticsearch.ssl.verificationMode
insteadRemoves the ability to use
elasticsearch.ssl.cert
and requires that the user useselasticsearch.ssl.certificate
insteadRemoves the ability to use
elasticsearch.ssl.ca
and requires that the user useselasticsearch.ssl.certificateAuthorities
insteadRemoves the ability to use
xpack.monitoring.elasticsearch.url
and requires that the user usesxpack.monitoring.elasticsearch.hosts
insteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.verify
and requires that the user usesxpack.monitoring.elasticsearch.ssl.verificationMode
insteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.cert
and requires that the user usesxpack.monitoring.elasticsearch.ssl.certificate
insteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.ca
and requires that the user usesxpack.monitoring.elasticsearch.ssl.certificateAuthorities
instead"Release Note:
elasticsearch.url
is no longer valid,elasticsearch.hosts
must be used instead. In prior versions of Kibana, if no port was specified inelasticsearch.url
a default of 9200 was chosen. The port inelasticsearch.hosts
is protocol dependent: https ports will use 443, and http ports will use 80.""Release Note:
elasticsearch.ssl.verify
is no longer valid,elasticsearch.ssl.verificationMode
must be used instead. Previously setelasticsearch.ssl.verify
is equal toelasticsearch.ssl.verificationMode: full
.""Release Note:
elasticsearch.ssl.cert
is no longer valid,elasticsearch.ssl.certificate
must be used instead.""Release Note:
elasticsearch.ssl.ca
is no longer valid,elasticsearch.ssl.certificateAuthorities
must be used instead.""Release Note:
xpack.monitoring.elasticsearch.url
is no longer valid,xpack.monitoring.elasticsearch.hosts
must be used instead. In prior versions of Kibana, if no port was specified inxpack.monitoring.elasticsearch.url
a default of 9200 was chosen. The port inxpack.monitoring.elasticsearch.hosts
is protocol dependent: https ports will use 443, and http ports will use 80.""Release Note:
xpack.monitoring.elasticsearch.ssl.verify
is no longer valid,xpack.monitoring.elasticsearch.ssl.verificationMode
must be used instead. Previously setxpack.monitoring.elasticsearch.ssl.verify
is equal toxpack.monitoring.elasticsearch.ssl.verificationMode: full
.""Release Note:
xpack.monitoring.elasticsearch.ssl.cert
is no longer valid,xpack.monitoring.elasticsearch.ssl.certificate
must be used instead.""Release Note:
xpack.monitoring.elasticsearch.ssl.ca
is no longer valid,xpack.monitoring.elasticsearch.ssl.certificateAuthorities
must be used instead."