-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't create opsgenie_service_incident_rule : 422 response #454
Comments
I have the same problem. Looks like API request expected by OG API has changed. Talking with the support currently. expected body is
However this returns 422. Support asked to add one layer of abstraction in the payload and this below then returns 200 but we need to work on this to reflect that change to the go file for TF module:
|
Maybe Solution would be something similar? |
This has been accepted as a bug by Atlassian after P1 for a customer has been reported by us, so perhaps fixing it here is not correct, as instead it may be fixed by Atlassian: https://jira.atlassian.com/browse/OPSGENIE-2359 |
Whatever works for them, sir. I just tried to help but still, they have the full context of what has happened and how to mitigate it. Proposal here maybe not the cleanest and long term solution, more on setting fire off. :) |
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
New incident rule should be created.
Actual Behavior
I also have tried without some of optional fields but result was all the same.
Additional notes
I was updating multiple Opsgenie repositories across our organization with mentioned changes. MRs which were merged previous week were applied without issues, afterwards we started experiencing this issue. Seems like something have changed in Opsgenie API during this period?
The text was updated successfully, but these errors were encountered: