[Alerting] embedding the flyout requires host solutions to manually require alerting deps

[gmmorris]

We should find a way to allow embedding the alerting flyouts without having to change code and manually extend dependencies whenever they're needed in the flyout.

[elasticmachine]

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

[pmuellr]

Why is this a problem? I think we want to allow for alerting / actions to be disable-able, so having embedders have an optional dependency on alerting seems reasonable. How else would they know alerting is enabled or not, to figure out whether or not to enable alerting flyouts?

I guess I'm not sure what without having to change code means ...

[mikecote]

This is in reference the flyout needing to be wrapped in a context provider. Each plugin that wants to use our flyout needs to require and pass in our dependencies (ex: http, docLinks, toastNotifications). Here's an example of what the metrics UI code needs to pass in order to use our flyout: https://github.com/elastic/kibana/blob/master/x-pack/plugins/infra/public/components/alerting/metrics/alert_flyout.tsx#L30-L42.

[pmuellr]

Ah passing in the deps as parameters! I got it, thx.

[mikecote]

Might be able to do at the same time as #65146?

[mikecote]

@gmmorris @YulNaumenko looks like this issue is resolved by #83248? Since the flyouts can be accessed via the plugin's start contract and no longer requires alerting dependencies.

[gmmorris]

@gmmorris @YulNaumenko looks like this issue is resolved by #83248? Since the flyouts can be accessed via the plugin's start contract and no longer requires alerting dependencies.

Yup, agreed :)