-
Notifications
You must be signed in to change notification settings - Fork 244
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
An initial implementation of client retries. #522
Conversation
fbde639
to
2dd9bb6
Compare
return nil, respErr | ||
} | ||
|
||
if resp.StatusCode < 200 || resp.StatusCode > 299 { |
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.
Do we want to return 3xx as an error?
Edit: I see that's the existing behaviour. Question is not a blocker.
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.
LGTM, minor comments.
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.
LGTM 👍🏽
Overview
Adds the ability to configure the client to retry certain types of failures.
Changes
When configured for retries:
Other Notes
Note that this functionality is not supported in the following API functions at this time:
pagerduty.CreateEvent
pagerduty.CreateEventWithHTTPClient
client.Do
This likely be optional functionality for the current 1.9 release. Please give us your feedback.