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.

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

[SIEM] Migrate to new platform #45831

Closed
26 tasks done
spong opened this issue Sep 16, 2019 · 5 comments
Closed
26 tasks done

[SIEM] Migrate to new platform #45831

spong opened this issue Sep 16, 2019 · 5 comments

Comments

@spong
Copy link
Member

spong commented Sep 16, 2019

This issue is for tracking the migration of the SIEM App to the Kibana New Platform. With the work done in re-bootstrapping the app for embeddables support, the only remaining Angular code is in mounting the SIEM App. Existing blockers are minimal and listed below. Intended timeline is to shim in 7.5, and migrate in 7.6 (blocker dependent). @XavierM and @spong will be leading the migration effort on the SIEM Team.

New Platform Migration Guide is located here.

Other Useful docs:

SIEM App Blockers:

Client
Server

Cutover Tasks

These steps need to be done during the process of moving the plugin into new platform.

UI
Server
  • replace legacy config with observable value
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem

@spong
Copy link
Member Author

spong commented Oct 31, 2019

For reference, client shim PR here: #48840

@rylnd
Copy link
Contributor

rylnd commented Mar 30, 2020

#59624 was the 7.7 spike to get SIEM to NP; there were a few issues preventing that from being merged during 7.7, but it should be unblocked for 7.8.

@joshdover
Copy link
Contributor

@spong @rylnd The Maps embeddable was migrated last week in #58178, so SIEM should be completely unblocked from migrating the UI to the Kibana Platform. If there are any other blockers please let the Platform Team know!

@spong
Copy link
Member Author

spong commented Apr 28, 2020

@rylnd just merged the client as part of #64251, so I think we're good to close this -- thanks for all the help along the way! 🙂

@spong spong closed this as completed Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants