[CSGI-2263] Support rate limiting throttling #777
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imjaroiswebdev
force-pushed
the
support-ratelimit-throttling
branch
from
397fa2d to
0f5c121
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #765, #760, #772
Points
heimweh/go-pagerdutyto updated version supporting graceful handling of new REST API rate limiting headers, throttling API calls blocked by http 429 errors, as recommended by PagerDuty during the amount of seconds noted in ratelimit-reset headers to retry the call afterwards.Additionally, removes delays on retries for
pagerduty_serviceandpagerduty_service_integrationwhich are not longer needed with new version ofheimweh/go-pagerduty.