‼️ Notice: (cli) sdk logging present even though verbose logging is not turned on #33320
Description
Please add your +1 👍 to let us know you have encountered this
Status: RESOLVED
Overview:
In v2.178.0 every CLI command is printing additional debug traces for AWS SDK calls.
Complete Error Message:
Example:
Workaround:
none, update to v2.178.1
Solution:
update to v2.178.1
Related Issues:
n/a
Describe the bug
When CDK Watch is used the SDK logger prints verbose logs continuously reducing the utility of CDK watch as it becomes difficult to view the lambda logs as invocations are made. This wasn't happening before. Based on the SDK logger code, it is supposed to print that if debug was true or trace was true or verbose was requested in the cli. In my case they are not set and uses the default. I also tried with debug as false, and trace as false and I was unable to reduce the verbosity.
Refer screenshot for details (The SDK Info log in my case prints continuously for the CloudWatch.FilterLogEvents)
Regression Issue
- Select this option if this issue appears to be a regression.
Last Known Working CDK Version
2.176.0
Expected Behavior
SDK Info logs is expected if debug, trace or verbose logging was requested.
Current Behavior
SDK Info logs are always present and it doesn't appear to be configurable.
Reproduction Steps
Running cdk watch on a stack
Possible Solution
If debug is false (default), trace is false (default) and verbose was not requested then SDK Logger should not print SDK Info logs in the CLI output.
Additional Information/Context
No response
CDK CLI Version
2.178.0
Framework Version
No response
Node.js Version
20
OS
Windows
Language
TypeScript
Language Version
5.x
Other information
No response