Should an alert action be assignable to multiple action groups?

[mikecote]

It was discussed while designing #64077 if an alert action should be assigned to more than a single action group. What this would mean is that you can provide a single message for different actions group of an alert (example: warning, alert).

The structure would change from:

actions: [
  {
    group: 'default',
    actionTypeId: '123',
    params: {},
  }
]

to:

actions: [
  {
    group: ['default', 'warning'],
    actionTypeId: '123',
    params: {},
  }
]

This may also need a mustache template variable to know what group the action is rendering for.

[elasticmachine]

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

[pmuellr]

Noting that this is a rare structure change that doesn't require a change to ES mappings (changing a field from a single to array value requires no ES mapping change).

However, it is a type change. We could probably change the TS type to string | string[], but then it will be rather messy to access, and long term we want it as string[]. So we may need some "migration" in the end, though we could probably just do it on the reading of the SO.

[YulNaumenko]

@arisonl do you have more concrete customers enhancements for this?