Fix changing the owner team of an API integration

[multani]

This is not supported by the API: https://docs.opsgenie.com/docs/integration-api#update-integration

Note that, if changed, this will recreate the API integration from scratch and will most likely change the API key associated with the integration: if it has been already installed somewhere, the integration will stop working until it has been updated where it has been installed.

Fix: #145

[multani]

@ffahri Any news on this?

I understand that recreating a brand new integration is not ideal, but were you able to raise this issue to the OpsGenie Development team to see if they could extend their API to support this type of use-case?

[kamilhristov]

@fnuva Please provide some input on this 🙏

Hitting the same problem and prefer re-creating the resource instead of silently ignoring the change.

[plaes]

It would be nice it it provides a warning message that would at least detect the drift (it seems that currently the existing state is not compared with state from OpsGenie) and suggest the user to either: a) fixing it manually in the OpsGenie UI (so you can continue using existing keys)... b) ...or suggest recreating the integration (which would blow up existing key)

We just ran into this after reassigning some of the keys without existing team and thus missed critical alerts.

[PrayagS]

Any updates on this? Seems like we might just have to run a fork if this isn't going anywhere. Thanks.

[Kerwood]

Any updates on this? Seems like we might just have to run a fork if this isn't going anywhere. Thanks.

Hmm, I wish that Atlassian/Opsgenie would put more working resources into their Terraform provider, which is obviously used by many of their customers.

This small PR shouldn't have gone unnoticed for two years.

[mlessig]

We are also having this issue.