Remove default retry logic to force clients to implement on their own #286
+52
−84
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
kag728
changed the title
misalcedo
previously approved these changes
Dec 6, 2023
misalcedo
reviewed
Dec 6, 2023
ndonewar
approved these changes
Dec 8, 2023
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.
This PR removes all default retry logic from elastomer-client, putting the burden on the consumer to implement retry logic using Faraday as they wish.
This removes
max_retriesandretry_delayparameters from the initialization since they're no longer used anywhere. This is a breaking change, and once merged, will require a major version upgrade of elsatomer-client.