Describe the feature
I just ran into #3081, where it was discussed that waiters retrying after 403 is by design and we have to add logger: console to make the problem visible.
I am so tired of AWS and its SDKs wasting so much of my time on stupid goose chases like this.
Why don't you just log errors like this by default and have that kind of logging be opt-out? Do you want us to suffer?
Use Case
Not wasting atrocious amounts of paying customers' time
Proposed Solution
Log errors like this to the console by default. If there could be sensitive information in the error at least periodically log something like the fact that 403s are happening. Require people who don't want this kind of logging to pass a flag to turn it off
Other Information
How about showing more interest and creativity in figuring out a way to improve DX when people run into problems like this? When people say they're tearing their hair out trying to figure out why something isn't working, no maintainer should feel content with just explaining all the reasons it's by design, unless they've wracked their brain trying to think of any possible way to make it less confusing and there's truly no way.
Acknowledgements
SDK version used
3.1000.0
Environment details (OS name and version, etc.)
N/A
Describe the feature
I just ran into #3081, where it was discussed that waiters retrying after 403 is by design and we have to add
logger: consoleto make the problem visible.I am so tired of AWS and its SDKs wasting so much of my time on stupid goose chases like this.
Why don't you just log errors like this by default and have that kind of logging be opt-out? Do you want us to suffer?
Use Case
Not wasting atrocious amounts of paying customers' time
Proposed Solution
Log errors like this to the console by default. If there could be sensitive information in the error at least periodically log something like the fact that 403s are happening. Require people who don't want this kind of logging to pass a flag to turn it off
Other Information
How about showing more interest and creativity in figuring out a way to improve DX when people run into problems like this? When people say they're tearing their hair out trying to figure out why something isn't working, no maintainer should feel content with just explaining all the reasons it's by design, unless they've wracked their brain trying to think of any possible way to make it less confusing and there's truly no way.
Acknowledgements
SDK version used
3.1000.0
Environment details (OS name and version, etc.)
N/A