-
Notifications
You must be signed in to change notification settings - Fork 402
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
feat(logger): introduce POWERTOOLS_DEBUG for internal debugging #1572
feat(logger): introduce POWERTOOLS_DEBUG for internal debugging #1572
Conversation
Codecov ReportBase: 99.74% // Head: 99.65% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1572 +/- ##
===========================================
- Coverage 99.74% 99.65% -0.09%
===========================================
Files 124 124
Lines 5772 5783 +11
Branches 656 658 +2
===========================================
+ Hits 5757 5763 +6
- Misses 8 11 +3
- Partials 7 9 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
merging as @rubenfonseca already approved changes earlier (stand-up) but is busy with V2 last Layer tests |
Issue number: aws-powertools/powertools-lambda#86
Summary
Changes
Introduces a new environment variable
POWERTOOLS_DEBUG
to more easily enable internal debugging for Powertools operations.User experience
BEFORE
AFTER
Simple use
POWERTOOLS_DEBUG
environment variable.Checklist
If your change doesn't seem to apply, please leave them unchecked.
POWERTOOLS_DEBUG
andPOWERTOOLS_DEV
strtobool
for most common values"1"
and"0"
for speedIs this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
View rendered docs/index.md