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
Hi,
It seems like the API allows the JSON value null (tested it via https://v2.developer.pagerduty.com/v2/page/api-reference#!/Services/put_services_id) to be passed which would disable the auto_resolve_timeout (as well as acknowledgement_timeout and possibly others) but it doesn't seem like the client library support it yet.
auto_resolve_timeout
acknowledgement_timeout
Here's a screenshot:
I'd be happy to help out on this one but not quite sure where to start.
The text was updated successfully, but these errors were encountered:
@heimweh current implementation uses an uint pointer https://github.com/PagerDuty/go-pagerduty/blob/master/service.go#L62 for the service struct. If you remove "omitempty" from the annotation of AutoResolveTimeout field, I think that will solve your use case.
Sorry, something went wrong.
@ranjib: thanks for looking into this. I'll take a look and see if I can get this to work. I think we need to cover three use cases though.
Is this something we want or do we want to just handle user-defined timeouts or have them disabled?
No branches or pull requests
Hi,
It seems like the API allows the JSON value null (tested it via https://v2.developer.pagerduty.com/v2/page/api-reference#!/Services/put_services_id) to be passed which would disable the
auto_resolve_timeout
(as well asacknowledgement_timeout
and possibly others) but it doesn't seem like the client library support it yet.Here's a screenshot:
I'd be happy to help out on this one but not quite sure where to start.
The text was updated successfully, but these errors were encountered: