Ability to register common variables that can be used in alert action templates

[mikecote]

Cloud would like to inject a few variables that any alert action can use. They would show up within the dropdown in the screenshot below.

[elasticmachine]

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

[pmuellr]

Thinking that we will probably want to add some kind of "registration" to allow a plugin to add new "built-in" variables in their setup/start - perhaps requiring a "top-level" name for them (eg, 'cloud' would expose 'cloud.deploymentId', ...).

As long as these values are static, the values could be provided at registration, otherwise we could allow a function to be associated with the variable, and call it as needed.

[mikecote]

^^ Agreed.

I also forgot to put an example for this requirement. Cloud would like to expose the cluster name, id, etc as alert action variables.

[mikecote]

Moving from 7.12 - Candidates to 7.x - Candidates.

[mikecote]

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

[mikecote]

Closing due to lack of interest.