We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Alert policies have an order and it's important as they match in a waterfall manner (https://docs.opsgenie.com/docs/alert-and-notification-policy-api#list-alert-policies)
It's not possible to set this as currently on the conditions within a policy can be ordered not the policies themselves (https://registry.terraform.io/providers/opsgenie/opsgenie/latest/docs/resources/alert_policy)
The text was updated successfully, but these errors were encountered:
fix opsgenie#398
501ecc7
specify order for opsgenie_alert_policy, use change-order endpoint to apply see https://docs.opsgenie.com/docs/alert-and-notification-policy-api#change-policy-order
Hi @jonfreedman, I'd love to be able to use a version this provider with your fix included. Have you opened a PR?
Sorry, something went wrong.
keen to have this
PR is here: #400
We're going to replace OpsGenie with PagerDuty
No branches or pull requests
Alert policies have an order and it's important as they match in a waterfall manner (https://docs.opsgenie.com/docs/alert-and-notification-policy-api#list-alert-policies)
It's not possible to set this as currently on the conditions within a policy can be ordered not the policies themselves (https://registry.terraform.io/providers/opsgenie/opsgenie/latest/docs/resources/alert_policy)
The text was updated successfully, but these errors were encountered: