-
Notifications
You must be signed in to change notification settings - Fork 26
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
chore: Powertools Logger v2 #832
Merged
hjgraca
merged 51 commits into
aws-powertools:develop
from
hjgraca:feature/logger-ilogger-instance
Apr 8, 2025
Merged
chore: Powertools Logger v2 #832
hjgraca
merged 51 commits into
aws-powertools:develop
from
hjgraca:feature/logger-ilogger-instance
Apr 8, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ver for enhanced logging capabilities
…te logging methods. revert systemwrapper, revert lambda.core to 2.5.0
…te logging methods. revert systemwrapper, revert lambda.core to 2.5.0
… configuration classes
…ations. ColdStart logic for provisioned-concurrency
…and common reference. Fix TypeInfoResolver
Bump logging package to 2.0.0-preview.1. Update documentation for v2. Add integration tests.
Signed-off-by: Henrique Graca <[email protected]>
…ambda.Powertools.Common project
|
leandrodamascena
approved these changes
Apr 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/common
Core Powertools utility
area/idempotency
area/logging
Core logging utility
documentation
Improvements or additions to documentation
internal
Maintenance changes
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: #229 | #230 | #374 | #425 | #417 | #496 | #497 | #783
Summary
Changes
In this pull request we are moving Logger to v2 and added the following features:
Project Configuration:
AOT-Function-ILogger
to the solution file (AWS.Lambda.Powertools.sln
). This includes adding the project reference and updating the build configurations. [1] [2] [3]ProjectReference
inAWS.Lambda.Powertools.BatchProcessing.csproj
so that it always includesAWS.Lambda.Powertools.Common.csproj
.Environment Handling:
AWSInitializationTypeEnv
inConstants.cs
for handling AWS Lambda initialization type.IConsoleWrapper
by removing theReadLine
method.IPowertoolsConfigurations
to track cold start and AWS initialization type.IPowertoolsEnvironment
to set the AWS execution environment.LambdaLifecycleTracker
to track Lambda lifecycle state including cold starts.PowertoolsConfigurations
to usePowertoolsEnvironment
for environment variable handling and added support for cold start and initialization type. [1] [2] [3] [4] [5] [6] [7] [8] [9]PowertoolsEnvironment
to set the AWS execution environment and parse assembly names. [1] [2]User experience
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is 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.