Actions & Embeddables Phase II API

[stacey-gammon]

• UI Actions local registries
• Serialize/deserialize actions
• Dynamic action configuration
• Embeddable event API
• Initialize dynamic actions (events)

---

Terms

• Event — trigger and action pair.
• Dynamic action — UI action that can be created by user at runtime, can be serialized/deserialized, can collect configuration using Phase II action configuration interface.

Parent issue: #42845

---

Summary

With "phase 1" of embeddables, there is a single registry for developers to implement custom action functionality in the UI by attaching Action instances to Triggers.

With "Phase 2", we would like to expose this functionality to end users (aka "Content creators"), not just developers. This would be specific for embeddables.

Implementation details

If Action A is not a singleton, and a factory for it exists, then the content creator can create multiple instances of that action, and attach them to the same trigger, for a given embeddable of the supported type.

It’s important to note that the content creator is creating these actions per embeddable instance, not embeddable type.

The system is pluggable so another developer can enter the mix and add new embeddable types, new action types, new triggers, but can also reuse existing triggers.

Mocks

cc @streamich

[elasticmachine]

Pinging @elastic/kibana-app-arch