Open smitthakkar96 opened 2 years ago
This is currently quite a significant limitation in the provider, as basically any non-standard integration features can't be customised via Terraform. This makes it effectively impossible to manage integrations with Terraform in its current state.
After looking into the API a bit, it seems the simplest & quickest solution would be to add an optional payload
field to the opsgenie_api_integration
that is just merged over the request payload data of the HTTP request. I assume this is done the same way for the optional headers
field, so we'd simply need one for the data/payload and it would be possible to fully configure the integration via Terraform.
This may be related to my problem -- I'm trying to integrate datadog and opsgenie, but I need to be able to get the API key out of a service so I can pass it to datadog, but there's no exported values on the service object. Is this the same thing?
any update?
In order to sent alerts back to Datadog, We need to configure the Datadog integration with API Key and Site (in case of eu it has to be https//api.datadoghq.eu/). Currently this is not possible. Since different integrations have different properties it would be great to split
opsgenie_api_integration
per type however this is a backwards incompatible change.