-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silent failure when there are no NoCredentialProviders #579
Comments
Ok, just saw #413, but looks like that's been rolled back in favor of #517. But when I use:
I still don't receive any logging output? |
Hello @josh-padnick, thank you for reaching out to us. I am curious to how you are attempting to grab the verbose errors. Are you grabbing the verbose errors by calling |
I was using Here's my full code:
This works fine, but it's non-obvious to have to do this test. It seems like |
Sorry, yes, I meant We can update the docs to be more explicit and add this to the backlog for the future. Thank you for the feedback and we'll do our best to make the use of the SDK more intuitive. |
Ah, got it. Yeah, docs would be a big help since I kept thinking there was something I was missing by not seeing any errors/logs/panics. Thanks for the prompt responsiveness! |
I've updated the github wiki to include an example of checking if credentials have been loaded properly. |
I've noticed that when I run the following code:
If no credentials are provided using the documented methods of specifying credentials, then there appears to be no
panic
or other interruption.I've also tried the
WithLogger()
option to specify anaws.Logger
and still don't see any log output onstdout
.Is this silent failure a known issue, or am I missing something? Also, I was thinking about calling credentials.Get() but then I see this error when there are no credentials defined:
So perhaps I don't want to use this error since it's deprecated?
Would appreciate some best-practices guidance here so users of my library receive nice error messages if they fail to specify credentials.
The text was updated successfully, but these errors were encountered: