-
Notifications
You must be signed in to change notification settings - Fork 4k
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
cli: sdk logging present even though verbose logging is not turned on #33320
Comments
getting the [SDK info] tag in the normal |
I just confirmed that the breaking change occurred in 2.178.0 - 2.177.0 works as expected. |
@blimmer I found this change in version 2.178.0 https://github.com/aws/aws-cdk/pull/33234/files which might be the root cause for the change in behavior. |
Looking into it. |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
Fix is merged. We are kicking off the release imminently, but it will take a few hours. |
Please add your +1 👍 to let us know you have encountered this
Status: IN-PROGRESS
Overview:
In v2.178.0 every CLI command is printing additional debug traces for AWS SDK calls.
Complete Error Message:
Example:
![Image](https://private-user-images.githubusercontent.com/33257049/410572751-b3208a19-1f12-4ae3-93f8-7fc57480d66a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MTgzOTcsIm5iZiI6MTczODkxODA5NywicGF0aCI6Ii8zMzI1NzA0OS80MTA1NzI3NTEtYjMyMDhhMTktMWYxMi00YWUzLTkzZjgtN2ZjNTc0ODBkNjZhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDA4NDgxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVmYTQ5MTdhMTkxMDJiYWI0Yzk1M2Q0YWYzMTE0MDY4M2UzZTRmYzE2ODcyODZlYzhlY2NiZmIzNGUxOGVlYzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.MpNyzlAJ-81HFjgFrMPe1L6gGMa1rAUBSAf24UlaHWY)
Workaround:
none, update to v2.178.1 (release in progress)
Solution:
update to v2.178.1 (release in progress)
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
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
The text was updated successfully, but these errors were encountered: