Bug: custom properties (extra properties) on opsgenie_alert_policy are discarded when any changes are made

[pieter-lautus]

On the web UI, when editing alert policies, one can click one "Add custom property" to add one or more extra properties in the form of a key value pair.

Our Opsgenie setup makes extensive use of extra properties, since our alerts originate from Prometheus, and every Prometheus alerts has a bunch of so-called "labels" that get mapped to extra properties on the OpsGenie side. We use these to drive OpsGenie policy, i.e. some of our Prometheus alerts have label "hours" with value "office_hours" and OpsGenie is supposed to implement the policy of postponing overnight alerts to office hours.

The current opsgenie_alert_policy has no support for these.

Affected Resource(s)

• opsgenie_alert_policy

[pieter-lautus]

This issue is worse than just a lack of support for setting custom properties on alert policies.

If the opsgenie_alert_policy makes any changes at all to an alert policy (say, to change the filter conditions), then any custom properties that were set on the alert property are discarded as part of the update.

[cecalero]

Hi, I have the same issue and then if I try to import them it isn't possible.
I need to include/edit/delete extra properties by Terraform.
@pieter-lautus Did you find a solution?

[pieter-lautus]

@cecalero Not really.

We refactored our OpsGenie setup to use P1..P5 priorities instead of the prometheus labels we were using before, so the solution we found was to not use custom properties in the first place.

[cecalero]

Ok, It isn't a solution for me. I need to include the extra-properties in terraform. Anyway Thanks,