-
Notifications
You must be signed in to change notification settings - Fork 212
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
Instantiate scheduled_actions if incident_urgency_rules with type = "use_support_hours" #99
Conversation
Test added and ready for a review. |
Acceptance test results
|
@heimweh I was debating where this should be fixed (in this provider here or in the api call in https://github.com/heimweh/go-pagerduty). I think this is the better of the two solutions, but am open to move this out to |
hi @heimweh anything else I should do here to have this PR ready to review? |
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.
Hi @sarkis, sorry for the delay here. I've been away for a couple of days.
Thank you so much for this!
This LGTM 👍
@heimweh no worries at all! I apologize for the spam... Thanks so much for this awesome provider. Hoping to help out with more open issues in the near future. |
@heimweh is there some set release cadence? I'm managing a couple of PRs in our terraform manifests that will require the change from this PR, so I wanted to check in to see when 1.3 may be released, before I set an expectation here. |
This fixes #97, instantiating scheduled actions if
use_support_hours
incident urgency type is set. It ensures that the pagerduty API calls will include an emptyscheduled_actions
in certain cases, explained better by the bug report in #97.