Repository navigation
Remove previously deprecated elasticsearch.* settings. - #29496
Conversation
|
Pinging @elastic/kibana-platform |
💚 Build Succeeded |
|
|
||
| *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.
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.
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! |
💚 Build Succeeded |
…elasticsearch.*` settings. (elastic#29496)
This PR:
Removes the ability to use
elasticsearch.urland requires that the user useselasticsearch.hostsinsteadRemoves the ability to use
elasticsearch.ssl.verifyand requires that the user useselasticsearch.ssl.verificationModeinsteadRemoves the ability to use
elasticsearch.ssl.certand requires that the user useselasticsearch.ssl.certificateinsteadRemoves the ability to use
elasticsearch.ssl.caand requires that the user useselasticsearch.ssl.certificateAuthoritiesinsteadRemoves the ability to use
xpack.monitoring.elasticsearch.urland requires that the user usesxpack.monitoring.elasticsearch.hostsinsteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.verifyand requires that the user usesxpack.monitoring.elasticsearch.ssl.verificationModeinsteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.certand requires that the user usesxpack.monitoring.elasticsearch.ssl.certificateinsteadRemoves the ability to use
xpack.monitoring.elasticsearch.ssl.caand requires that the user usesxpack.monitoring.elasticsearch.ssl.certificateAuthoritiesinstead"Release Note:
elasticsearch.urlis no longer valid,elasticsearch.hostsmust be used instead. In prior versions of Kibana, if no port was specified inelasticsearch.urla default of 9200 was chosen. The port inelasticsearch.hostsis protocol dependent: https ports will use 443, and http ports will use 80.""Release Note:
elasticsearch.ssl.verifyis no longer valid,elasticsearch.ssl.verificationModemust be used instead. Previously setelasticsearch.ssl.verifyis equal toelasticsearch.ssl.verificationMode: full.""Release Note:
elasticsearch.ssl.certis no longer valid,elasticsearch.ssl.certificatemust be used instead.""Release Note:
elasticsearch.ssl.cais no longer valid,elasticsearch.ssl.certificateAuthoritiesmust be used instead.""Release Note:
xpack.monitoring.elasticsearch.urlis no longer valid,xpack.monitoring.elasticsearch.hostsmust be used instead. In prior versions of Kibana, if no port was specified inxpack.monitoring.elasticsearch.urla default of 9200 was chosen. The port inxpack.monitoring.elasticsearch.hostsis protocol dependent: https ports will use 443, and http ports will use 80.""Release Note:
xpack.monitoring.elasticsearch.ssl.verifyis no longer valid,xpack.monitoring.elasticsearch.ssl.verificationModemust be used instead. Previously setxpack.monitoring.elasticsearch.ssl.verifyis equal toxpack.monitoring.elasticsearch.ssl.verificationMode: full.""Release Note:
xpack.monitoring.elasticsearch.ssl.certis no longer valid,xpack.monitoring.elasticsearch.ssl.certificatemust be used instead.""Release Note:
xpack.monitoring.elasticsearch.ssl.cais no longer valid,xpack.monitoring.elasticsearch.ssl.certificateAuthoritiesmust be used instead."