This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Handle rate limiting with a retryable http client #109
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
I was having trouble using the provider because I was being rate limited, and the error was "null" because it wasn't in json. This change adds the hashicorp retryable http client which will understand the 429s and exponentially backoff. Additionally, if there is anything else weird that happens that results in a non-200 or bad json, the error will be more visible to the user.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I was having trouble using the provider because I was being
rate limited, and the error was "null" because it wasn't in json.
This change adds the hashicorp retryable http client which will
understand the 429s and exponentially backoff.
Additionally, if there is anything else weird that happens that
results in a non-200 or bad json, the error will be more visible
to the user.