-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Task Manager] [8.0] Remove xpack.task_manager.index
#108111
[Task Manager] [8.0] Remove xpack.task_manager.index
#108111
Conversation
xpack.task_manager.index
Pinging @elastic/kibana-alerting-services (Team:Alerting 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! Should remove the setting from the 8.0 docs as well: https://www.elastic.co/guide/en/kibana/master/task-manager-settings-kb.html
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
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
This change has broken the test/dev infrastructure for Observability where we depend on this setting for multiple developers to all point their Kibana instances to the same ES cluster. I know that this has been planned for a while, but we are in the middle of our migration to CCS for our test infrastructure as a permanent work-around but that work has not yet been completed. We've been watching the issue that were were asked to watch for status updates for these changes but didn't see any mention of this change. I understand that it's not ideal, but is Kibana willing to temporarily revert this change for the next several weeks? We've been making steady progress on our migration but we just need more time. cc: @kobelb |
@cachedout Thanks for bringing this up! I wasn't aware of this dependency. I'll talk with the team and figure out the best path forward and update you on this PR. |
Thanks, @chrisronline ! I also posted in #82020 so you can also post your reply there if it brings more visibility. |
…)" This reverts commit 9dce033.
Resolves #102076
Related to #101964
Note: This PR should only live in 8.0 and not in 7.x
This setting is currently deprecated in 7.x and this PR removes it from 8.0.
Release note
Details
The
xpack.task_manager.index
setting is no longer supported as a configuration option.Impact
Users will need to remove
xpack.task_manager.index
from their Kibana config or Kibana will fail to start.