Allow disabling service incident timeouts (take 2) #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #51 (and #41 for good).
Checklist:
Rationale:
This PR changes
auto_resolve_timeout
andacknowledgement_timeout
fields fromint
tostring
type to allow passing a "null" value which means disabled as documented at https://v2.developer.pagerduty.com/v2/page/api-reference#!/Services/post_servicesMy previous fix in #44 did not work as expected as 0 effectively means 0 second, resulting in incidents to be instantaneously marked as resolved.
To avoid backward incompatible changes to existing terraform configurations, I preserved the default API values of 4h for
auto_resolve_timeout
and 30 minutes foracknowledgement_timeout
.Note that those are not explicitely stated in the v2 API documentation so I got them from the API v1: https://v1.developer.pagerduty.com/documentation/rest/services/create
I'm preparing a PR for go-pagerduty to remove the local vendor patch.
Acceptance tests results: