You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this scenario, -v seems to have no effect. It's the same as omitting the parameter. I don't think that's a useful customer experience. If I'm using the default, but not getting enough info, I start by using -v and nothing changes. I recommend that the default (nothing), be errors only.
The verbosity flag controls how the logger is configured.
Current verbosity behavior is:
-v
: WARN (global)-vv
: INFO (global)-vvv
: DEBUG (global)After going through various scenarios and using the logging output, I decided a more useful approach would be:
aws_encryption_sdk_cli
), CRITICAL (root)-v
: INFO (aws_encryption_sdk_cli
), CRITICAL (root)-vv
: DEBUG (aws_encryption_sdk_cli
), CRITICAL (root)-vvv
: DEBUG (aws_encryption_sdk_cli
), INFO (root)-vvvv
: DEBUG (aws_encryption_sdk_cli
), DEBUG (root)WARN is always on for safety reasons: we want users to always be aware of WARN events.
The text was updated successfully, but these errors were encountered: