Fixes Opsgenie Create Alert failure when external image URL attached #78
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue: grafana/grafana#67177
When invoking the Opsgenie Create Alert API, the field
detail
seems to only accept string value, does not accept array in the value. If the value is an array, Opsgenie will respond with 422 Unprocessable Entity.This fix converts the array to a comma joined string, and the following screenshot is a successfully sent alert with two images attached:
The following section is copied from the original issue:
What happened:
Cannot create Opsgenie Alerts with S3 image url attached
What you expected to happen:
Opsgenie Alerts are created and image URL are attached in details section
How to reproduce it (as minimally and precisely as possible):