-
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
[Telemetry] Deprecate telemetry url configs #96761
Labels
Breaking Change
Feature:Telemetry
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
v8.0.0
Comments
Bamieh
added
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Feature:Telemetry
v8.0.0
Team:KibanaTelemetry
Breaking Change
labels
Apr 12, 2021
Pinging @elastic/kibana-core (Team:Core) |
Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry) |
We need to sync with the QA and Cloud teams as they are setting those configs when deploying dev, QA and staging deployments. |
Ahh too many meta issues 🙃 I've added it. @afharo yes we need to communicate this breaking change along with all the other breaking changes we'll be shipping in 8.0 |
6 tasks
Merged
4 tasks
33 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Breaking Change
Feature:Telemetry
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
v8.0.0
We have no useful cases for changing the actual telemetry urls for deployments.
I suggest we deprecate the telemetry url configs (
telemetry.url
andtelemetry.optInStatusUrl
) in favor of atelemetry.staging: boolean
config. The url paths will be handled internally by the service.This would be a breaking change for
8.0.0
. We'd need to propogate this change internally as well across our testing environments.The text was updated successfully, but these errors were encountered: