-
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
Deprecate xpack.telemetry.* instead of removing it #51117
Conversation
While telemetry plugin has moved and its configurations no longer have the xpack prefix, for the time being we should only warn when we encounter the existing config names rather than blocking startup entirely.
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
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
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.
Code LGTM
LGTM: I tested the original bug and saw the fix in effect |
@Bamieh Let me know tomorrow if you have concerns or know of problems with this approach, but in the meantime I'm going to proceed with merging this if we get CI green. |
LGTM. Tested the deprecated setting xpack.telemetry.enabled and then removed it and tested the new setting telemetry.enabled. cc @LeeDr |
💚 Build Succeeded |
While telemetry plugin has moved and its configurations no longer have the xpack prefix, for the time being we should only warn when we encounter the existing config names rather than blocking startup entirely.
While telemetry plugin has moved and its configurations no longer have the xpack prefix, for the time being we should only warn when we encounter the existing config names rather than blocking startup entirely.
While telemetry plugin has moved and its configurations no longer have
the xpack prefix, for the time being we should only warn when we
encounter the existing config names rather than blocking startup
entirely.
Fixes #51064