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

Alerting team remaining Kibana Platform migration items #61379

Closed
10 of 11 tasks
mikecote opened this issue Mar 25, 2020 · 5 comments · Fixed by #64335
Closed
10 of 11 tasks

Alerting team remaining Kibana Platform migration items #61379

mikecote opened this issue Mar 25, 2020 · 5 comments · Fixed by #64335
Assignees
@gmmorris
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Mar 25, 2020 •
edited by gmmorris
Loading

Most if not all of the bullets below can be solved with Kibana Platform APIs today

Action plugin

  • mappings.json
  • config

Alerting plugin

  • mappings.json
  • config

Triggers Actions UI plugin

  • config
  • SCSS / publicDir

Task Manager plugin
@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Mar 25, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@gmmorris gmmorris self-assigned this Apr 23, 2020
@gmmorris gmmorris mentioned this issue Apr 23, 2020
Merged
7 tasks
@gmmorris
Copy link
Contributor

gmmorris commented Apr 24, 2020 •
edited
Loading

We still have some migrations to do here, but not this issue will be blocked by the legacy siem plugin:

kibana/x-pack/legacy/plugins/siem/index.ts

Line 20 in 6bb7515

require: ['kibana', 'elasticsearch', 'alerting', 'actions', 'triggers_actions_ui'],

I'll talk to the siem team to see what their timeline is

Update:
I spoke to siem and it's left over requirements, the plugin doesn't actually rely on the legacy plugins so I'm removing the deps in this PR.

@mikecote
Copy link
Contributor Author

@gmmorris can they access what they need via the following?

  • server.newPlatform.setup.plugins
  • server.newPlatform.start.plugins

@gmmorris
Copy link
Contributor

gmmorris commented Apr 24, 2020 •
edited
Loading

@gmmorris can they access what they need via the following?

  • server.newPlatform.setup.plugins
  • server.newPlatform.start.plugins

Turns out they aren't actually using the legacy plugins they just forgot the deps - I've removed the deps as part of this PR

@gmmorris gmmorris removed the blocked label Apr 24, 2020
@gmmorris
Copy link
Contributor

gmmorris commented Apr 27, 2020 •
edited
Loading

Looks like #56537 will have to be done before this issue is completed, as the legacy fixture plugins can't be supported without a legacy TM plugin in place.

To address this the TM removal will happen as part of a PR for that issue instead.

@gmmorris gmmorris added blocked and removed blocked labels Apr 27, 2020
@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

@gmmorris gmmorris

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerting] migrates all remaining plugins to new platform gmmorris/kibana
4 participants
@gmmorris @kobelb @mikecote @elasticmachine