Return alert id (iid) in POST responses for generic HTTP Endpoints

Release notes

When you POST an alert using a generic HTTP Endpoint the response is a simple 200 upon a successful POST. Internal teams hoping to dogfood alerts want to reconcile their current processes and would like to see additional information returned in the response, i.e. alert_id.

Problem to solve

When you POST an alert using a generic HTTP Endpoint the response is a simple 200 upon a successful POST. Internal teams hoping to dogfood alerts want to reconcile their current processes and would like to see additional information returned in the response, i.e. alert_id.

MVC Solution

Include alert_id in the response for generic HTTP Endpoint POST.

Long term solution

Not included in this MVC, but things that need to be considered:

• Create a REST API for alerts. This will allow for more access privileges (e.g. read/write complete API) than HTTP integration tokens do.
• Reconcile what is already available in the GraphQL API