Skip to content
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

Merged

Conversation

azasypkin
Copy link
Member

@azasypkin azasypkin commented Jan 29, 2019

This PR:

  • Removes the ability to use elasticsearch.url and requires that the user uses elasticsearch.hosts instead

  • Removes the ability to use elasticsearch.ssl.verify and requires that the user uses elasticsearch.ssl.verificationMode instead

  • Removes the ability to use elasticsearch.ssl.cert and requires that the user uses elasticsearch.ssl.certificate instead

  • Removes the ability to use elasticsearch.ssl.ca and requires that the user uses elasticsearch.ssl.certificateAuthorities instead

  • Removes the ability to use xpack.monitoring.elasticsearch.url and requires that the user uses xpack.monitoring.elasticsearch.hosts instead

  • Removes the ability to use xpack.monitoring.elasticsearch.ssl.verify and requires that the user uses xpack.monitoring.elasticsearch.ssl.verificationMode instead

  • Removes the ability to use xpack.monitoring.elasticsearch.ssl.cert and requires that the user uses xpack.monitoring.elasticsearch.ssl.certificate instead

  • Removes the ability to use xpack.monitoring.elasticsearch.ssl.ca and requires that the user uses xpack.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 in elasticsearch.url a default of 9200 was chosen. The port in
elasticsearch.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 set elasticsearch.ssl.verify is equal to elasticsearch.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 in xpack.monitoring.elasticsearch.url a default of 9200 was chosen. The port in
xpack.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 set xpack.monitoring.elasticsearch.ssl.verify is equal to xpack.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."

@azasypkin azasypkin added release_note:breaking Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.0.0 labels Jan 29, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@elasticmachine
Copy link
Contributor

💚 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]
Copy link
Member Author

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 @@
/*
Copy link
Member Author

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.

@azasypkin
Copy link
Member Author

Hey @elastic/stack-monitoring, we've recently removed deprecated server.ssl.cert and going to remove deprecated elasticsearch.ssl.cert/ca/verify in this PR. It'd probably make sense to do the same for xpack.monitoring.elasticsearch.* for the consistency sake in 7.0, what do you think?

@ycombinator
Copy link
Contributor

ycombinator commented Jan 29, 2019

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

@azasypkin
Copy link
Member Author

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.

If I'm not mistaken xpack.monitoring.elasticsearch.ssl.ca, xpack.monitoring.elasticsearch.ssl.cert and xpack.monitoring.elasticsearch.ssl.verify have been deprecated since 5.5 and xpack.monitoring.elasticsearch.hosts since 6.6.

@chrisronline
Copy link
Contributor

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?

@azasypkin
Copy link
Member Author

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?

@chrisronline
Copy link
Contributor

@azasypkin Agreed. Thanks!

Copy link
Contributor

@spalger spalger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:breaking Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Monitoring Stack Monitoring team v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants