search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.58k stars 8.21k forks source link

[RAM] Move actions UI into its own kbn package #152021

Open Zacqary opened 1 year ago

Zacqary commented 1 year ago

Move the UI components responsible for creating and editing actions into an importable KBN package outside of triggersActionsUI.

Right now, the Action Form is exported from the Triggers Actions UI plugin with the getActionForm function. Moving the UI components would be fairly straightforward, though there's quite a lot to move. Several components pull methods from the Triggers Actions UI lib and common folders, and these would all have to be moved or copied.

The more complicated problem is that they rely heavily on the actionTypeRegistry which has to be a part of the Triggers Actions UI plugin. Components in the Action Form hierarchy also make extensive use of useKibana services such as http and application capabilities. We'll need to require all of these to be passed in as props, or use some kind of a context wrapper.

elasticmachine commented 1 year ago

Pinging @elastic/response-ops (Team:ResponseOps)

Zacqary commented 1 year ago

Blocking this. See comments on https://github.com/elastic/kibana/issues/152021

Zacqary commented 1 year ago

Unblocking. Updated description and moved back to On Hold.