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.

Sign up for GitHub

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

Jump to bottom

Use new elasticsearch-js client everywhere and remove usage of legacy client #50247

Closed
mikecote opened this issue Nov 12, 2019 · 2 comments · Fixed by #93364
Closed

Use new elasticsearch-js client everywhere and remove usage of legacy client #50247

mikecote opened this issue Nov 12, 2019 · 2 comments · Fixed by #93364
Assignees
@YulNaumenko
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Nov 12, 2019 •
edited
Loading

See: #35508

  • This should also remove dependencies on the legacy client internally
  • This should also remove callCluster from the list of available services
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@justinkambic justinkambic mentioned this issue Oct 16, 2020
Merged
8 tasks
@mikecote mikecote changed the title Use new elasticsearch-js client for alert / action type executors Use new elasticsearch-js client everywhere in alerting team owned plugins Nov 20, 2020
@mikecote mikecote changed the title Use new elasticsearch-js client everywhere in alerting team owned plugins Use new elasticsearch-js client everywhere and remove usage of legacy client Nov 20, 2020
@mikecote mikecote mentioned this issue Nov 20, 2020
Closed
74 tasks
@mikecote mikecote mentioned this issue Dec 18, 2020
Merged
@gmmorris gmmorris mentioned this issue Jan 26, 2021
Merged
6 tasks
@mikecote
Copy link
Contributor Author

mikecote commented Feb 5, 2021

Moving from 7.x - Candidates to 7.13 after the latest 7.x planning session.

@YulNaumenko YulNaumenko self-assigned this Mar 1, 2021
@YulNaumenko YulNaumenko mentioned this issue Mar 3, 2021
Merged
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
5 participants
@kobelb @bmcconaghy @mikecote @elasticmachine @YulNaumenko