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
Modernizing our logging capabilities to align with .NET practices and improve developer experience.
26
27
28
+
-[ ] Logger buffer implementation
29
+
-[ ] New .NET-friendly API design (Serilog-like patterns)
30
+
-[ ] Correlation ID support via decorator/middleware
31
+
-[ ] JMESPath expression support
32
+
-[ ] RFC: Documentation for SDK context.Logger vs Powertools Logger differences
27
33
28
-
#### Security and Production Readiness (P1)
34
+
#### Metrics V2
29
35
30
-
- .NET 10 support
31
-
- .NET 6 deprecation
32
-
- OpenSSF Scorecard
36
+
Updating metrics implementation to support latest EMF specifications and improve performance.
33
37
34
-
#### Feature Parity (P2)
38
+
-[ ] Update to latest EMF specifications
39
+
-[ ] Breaking changes implementation
40
+
-[ ] Performance optimizations
41
+
-[ ] API updates
35
42
36
-
Feature parity with Powertools for AWS Lambda (Python):
37
-
- Data masking
38
-
- Feature Flags
39
-
- Streeaming from S3
43
+
### Security and Production Readiness (P1)
40
44
41
-
#### Support for ASP.NET
45
+
Ensuring enterprise-grade security and compatibility with latest .NET developments.
42
46
43
-
Support AspNetCoreServer.Hosting this allows customers to deploy ASP.NET core applicaiton to Lambda, [more details](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/360){target="_blank"}
47
+
-[ ] .NET 10 support from day one
48
+
-[ ] Deprecation path for .NET 6
49
+
-[ ] Security and best practices
50
+
-[ ] Scorecard implementation
51
+
-[ ] Security compliance checks
44
52
53
+
### Feature Parity and ASP.NET Support (P2)
54
+
55
+
#### Feature Parity
56
+
57
+
Implementing key features to achieve parity with other Powertools implementations.
58
+
59
+
-[ ] Data masking
60
+
-[ ] Feature Flags
61
+
-[ ] S3 Streaming support
62
+
63
+
#### ASP.NET Support
64
+
65
+
Adding first-class support for ASP.NET Core in Lambda with performance considerations.
-[ ] Clear guidance on Middleware vs. Decorators usage
45
72
46
73
#### Improve operational excellence
47
74
@@ -90,9 +117,9 @@ graph LR
90
117
Our end-to-end mechanism follows four major steps:
91
118
92
119
***Feature Request**. Ideas start with a [feature request](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/new?assignees=&labels=feature-request%2Ctriage&projects=&template=feature_request.yml&title=Feature+request%3A+TITLE){target="_blank"} to outline their use case at a high level. For complex use cases, maintainers might ask for/write a RFC.
93
-
* Maintainers review requests based on [project tenets](index.md#tenets){target="_blank"}, customers reaction (👍), and use cases.
120
+
* Maintainers review requests based on [project tenets](index.md#tenets){target="_blank"}, customers reaction (👍), and use cases.
94
121
***Request-for-comments (RFC)**. Design proposals use our [RFC issue template](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/new?assignees=&labels=RFC%2Ctriage&projects=&template=rfc.yml&title=RFC%3A+TITLE){target="_blank"} to describe its implementation, challenges, developer experience, dependencies, and alternative solutions.
95
-
* This helps refine the initial idea with community feedback before a decision is made.
122
+
* This helps refine the initial idea with community feedback before a decision is made.
96
123
***Decision**. After carefully reviewing and discussing them, maintainers make a final decision on whether to start implementation, defer or reject it, and update everyone with the next steps.
97
124
***Implementation**. For approved features, maintainers give priority to the original authors for implementation unless it is a sensitive task that is best handled by maintainers.
0 commit comments