-
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
Support for immediate notification #396
Support for immediate notification #396
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@koushik-swaminathan Any news in that regard? The change looks promising, would like to see it in the final code 😁 |
@koushik-swaminathan Do you see a chance to implement this improvement/bugfix in the near future? |
@stp-bsh there's some changed in the go-sdk as well, I will merge this PR once those changes have been merged. |
da0e354
to
9cd60a9
Compare
@stp-bsh, PR has been merged, the latest release should support 0 value for send_after. |
@koushik-swaminathan Thank you! |
@koushik-swaminathan Once again thank you for fixing it, but unfortunately there is only a tag v0.6.33 but no release available. Because of that the new version can't be used in terraform. Is there any chance to have the new release in the near future? versus |
Hi @stp-bsh, it was under draft, I have released the latest version now! |
Hello! resource "opsgenie_notification_rule" "P5-notifications" {
name = "P5 Notification"
username = data.opsgenie_user.admins["***"].username
action_type = "create-alert"
steps {
send_after = 0
contact {
method = "email"
to = "***"
}
}
criteria {
type = "match-any-condition"
conditions {
field = "priority"
operation = "equals"
expected_value = "P5"
}
}
order = 100
time_restriction {
type = "time-of-day"
restriction {
start_hour = 10
start_min = 0
end_hour = 19
end_min = 0
}
}
}
And after
|
Allows send_after field to be set as 0 for immediate notification.