Fixed ambiguous error message raised when resolving region from IMDS #9073
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
ashovlin
approved these changes
Nov 13, 2024
There was a problem hiding this comment.
👍 looks like same pattern we have here:
aws-cli/awscli/botocore/utils.py
Lines 530 to 531 in 8916d37
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.
An issue raised in #8988 points out an unhandled error in the AWS CLI region fetcher. In the base IMDS credential fetcher, this is handled by adding a debug log and turning the request into a no-op. In the CLI's region fetcher, it's treated as terminal and surfaced to the end user with an unhelpful object reference.
This was later ported to botocore in a different location (
botocore/utils.py). I'll address that in a separate PR upstream.