fix: Improve logging on failures to fetch secret #184
Merged
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.
What was the problem/requirement? (What/Why)
The logging around
get_secret_value
previously gave the customer no indication as to what might be wrong.What was the solution? (How)
Making sure
AccessDeniedException
is not swallowed and customers are given some information on how to resolve failures.What is the impact of this change?
See above.
How was this change tested?
Unit tests.
Was this change documented?
NA.
Is this a breaking change?
No.