Introduce settings flag to stop execution if expired credentials error happen #23
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
|
|
|
@Dziman anyway we can help to get this merged? |
|
We encountered this issue as well, this patch really helps to prevent the system to get into a incomplete state. |
This was referenced Feb 14, 2023
|
@Dziman Thank you very much for your work on this so long ago! We apologize for the delay. In essence, AWS fixed this problem so we did not end up needing the approach that you took. |
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.
Changes proposed in this pull request:
Introduce new settings parameter to stop retrying if AWS credentials are expired. To keep existing behavior (retry MaxRetries times) defaulted to false