Connectors to support multiple actions

[mikecote]

There are requests from the case team (cc @XavierM) to have a single connector able to do more than one thing. For example, ServiceNow should support create incident, add comment, update incident, delete incident, etc as actions, commands or functions of the connector while sharing the same credentials (config & secrets).

cc @pmuellr for further ideas / comments.

---

We had a call to discuss this on the 25th of June and came up with the following direction:

• Turn this issue into a meta issue to track the different steps we'd like to take towards achieving this requirement.
• Align the terminology in the code with the terminology we use externally and in the UI by changing "Actions" to "Connectors". This isn't a whole sale find-and-replace, as we'll still have an Actions feature, client etc. But we'll separate between the Connector entity and the Action entity as they are treated differently in the UI. The Actions terminology in the code has diverged from the terminology we use verbally and in the UI #70082
• Make it possible for an ActionType (which by that point might be a ConnectorType) to register multiple executors each of which represents a potential kind of action that might be taken using the connector. It isn't possible to reuse a single connector across multiple actions #70083
• RBAC for connectors/actions such that you can (perhaps) apply different privileges across these actions. It isn't possible to assign different privileges to different actions when they are based off of the same connector #70084

[elasticmachine]

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

[gmmorris]

Updated description now that the issue is a Meta issue

[mikecote]

cc @arisonl

[cnasikas]

@mikecote I think the third item is covered by the Subactions framework, right?

[mikecote]

@mikecote I think the third item is covered by the Subactions framework, right?

This issue is old 😄 (pre subaction framework days). Maybe we use this issue to merge the subactions framework into the main framework and the third item is to make multiple executors / subactions a first class feature on the connector type?