Surface relationships between Saved Objects when saving

[tbragin]

When you edit a visualization or saved search, you do not know what objects it may affect. It would be nice to have a confirmation dialog explicitly telling the user that this action will affect a list of objects, with an "OK" or "Cancel" as options.

[simianhacker]

I wonder if we should get away from the browser "confirmation" window and use something custom so we can add formatting. I can image that list of affected components could get pretty big.

[spalger]

@simianhacker I totally support using custom alerts/dialogs/modals vs using the built-in browser confirm() alert, but I agree that it's a large change (all of our current confirmation logic would need to be converted from sync to async for example).

[cjcenizal]

Just want to note that this issue is focused on communicating the relationships between Saved Objects, not necessarily the UI vehicle for doing so (e.g. confirmation modal).

[tbragin]

@cjcenizal related to this? #8804

[elasticmachine]

Pinging @elastic/kibana-platform

[rudolf]

Closing since #28199 adds the ability for Saved Objects to define references and these can be surfaced in the UI should plugins wish to expose this.