From 5bbc9699928664640e20d05ff38899c3f9e94a93 Mon Sep 17 00:00:00 2001 From: Henrique Graca <999396+hjgraca@users.noreply.github.com> Date: Mon, 10 Feb 2025 11:32:16 +0000 Subject: [PATCH 1/5] Update roadmap.md --- docs/roadmap.md | 45 +++++++++++++++++++++++++++++++++++++-------- 1 file changed, 37 insertions(+), 8 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 678853a0..3e6e2cb6 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -1,20 +1,49 @@ +--- +title: Roadmap +description: Public roadmap for Powertools for AWS Lambda (.NET) +--- + + + ## Overview -This is our public roadmap that outlines the high level direction we are working towards, namely [Themes](#themes). We update this document when our priorities change: security and stability is our top priority. +Our public roadmap outlines the high level direction we are working towards. We update this document when our priorities change: security and stability are our top priority. + +!!! info "For most up-to-date information, see our [board of activities](https://github.com/orgs/aws-powertools/projects/6/views/14?query=is%3Aopen+sort%3Aupdated-desc){target="_blank"}." + +### Key areas + +Security and operational excellence take precedence above all else. This means bug fixing, stability, customer's support, and internal compliance may delay one or more key areas below. +**Missing something or want us to prioritize an existing area?** +You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-dotnet/issues?q=is%3Aissue%20state%3Aopen%20label%3Afeature-request){target="_blank"}, leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord. + +[![Join our Discord](https://dcbadge.vercel.app/api/server/B8zZKbbyET)](https://discord.gg/B8zZKbbyET){target="_blank"} + +#### Logging v2 (P0) + + +#### Metrics v2 (P0) + + +#### Security and Production Readiness (P1) -[See our latest list of activities ยป](https://github.com/orgs/aws-powertools/projects/6/views/4?query=is%3Aopen+sort%3Aupdated-desc){target="_blank"} +- .NET 10 support +- .NET 6 deprecation +- OpenSSF Scorecard -## Themes +#### Feature Parity (P2) -!!! info "Operational Excellence is priority number 1." +Feature parity with Powertools for AWS Lambda (Python): +- Data masking +- Feature Flags +- Streeaming from S3 -Themes are key activities maintainers are focusing on, besides bug reports. These are updated periodically and you can get an idea of the overall progress in the [Milestones section](https://github.com/aws-powertools/powertools-lambda-dotnet/milestones){target="_blank"}. +#### Support for ASP.NET -### New utilities +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"} -After going GA, we want to start working on new utilities, specifically but not limited to the most commonly asked: **(1)** [Idempotency](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/164), **(2)** [Parameters](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/160) and **(3)** [Batch](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/168). -### Improve operational excellence +#### Improve operational excellence We continue to work on increasing operational excellence to remove as much undifferentiated heavylifting for maintainers, so that we can focus on delivering features that help you. From ce793707a823fe17f739eb1353ec706cfda7db3e Mon Sep 17 00:00:00 2001 From: Henrique Graca <999396+hjgraca@users.noreply.github.com> Date: Tue, 11 Feb 2025 10:01:39 +0000 Subject: [PATCH 2/5] Update roadmap.md --- docs/roadmap.md | 57 ++++++++++++++++++++++++++++++++++++------------- 1 file changed, 42 insertions(+), 15 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 3e6e2cb6..7e55e489 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -19,29 +19,56 @@ You can help us prioritize by [upvoting existing feature requests](https://githu [![Join our Discord](https://dcbadge.vercel.app/api/server/B8zZKbbyET)](https://discord.gg/B8zZKbbyET){target="_blank"} -#### Logging v2 (P0) +### Core Utilities (P0) +#### Logging V2 -#### Metrics v2 (P0) +Modernizing our logging capabilities to align with .NET practices and improve developer experience. +- [ ] Logger buffer implementation +- [ ] New .NET-friendly API design (Serilog-like patterns) +- [ ] Correlation ID support via decorator/middleware +- [ ] JMESPath expression support +- [ ] RFC: Documentation for SDK context.Logger vs Powertools Logger differences -#### Security and Production Readiness (P1) +#### Metrics V2 -- .NET 10 support -- .NET 6 deprecation -- OpenSSF Scorecard +Updating metrics implementation to support latest EMF specifications and improve performance. -#### Feature Parity (P2) +- [ ] Update to latest EMF specifications +- [ ] Breaking changes implementation +- [ ] Performance optimizations +- [ ] API updates -Feature parity with Powertools for AWS Lambda (Python): -- Data masking -- Feature Flags -- Streeaming from S3 +### Security and Production Readiness (P1) -#### Support for ASP.NET +Ensuring enterprise-grade security and compatibility with latest .NET developments. -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"} +- [ ] .NET 10 support from day one +- [ ] Deprecation path for .NET 6 +- [ ] Security and best practices +- [ ] Scorecard implementation +- [ ] Security compliance checks +### Feature Parity and ASP.NET Support (P2) + +#### Feature Parity + +Implementing key features to achieve parity with other Powertools implementations. + +- [ ] Data masking +- [ ] Feature Flags +- [ ] S3 Streaming support + +#### ASP.NET Support + +Adding first-class support for ASP.NET Core in Lambda with performance considerations. + +- [ ] AspNetCoreServer.Hosting - [Tracking issue](https://github.com/aws-powertools/powertools-lambda-dotnet/issues/360){target="_blank"} +- [ ] Minimal APIs support +- [ ] ASP.NET Core integration +- [ ] Documentation for cold start impacts +- [ ] Clear guidance on Middleware vs. Decorators usage #### Improve operational excellence @@ -90,9 +117,9 @@ graph LR Our end-to-end mechanism follows four major steps: * **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. - * Maintainers review requests based on [project tenets](index.md#tenets){target="_blank"}, customers reaction (๐Ÿ‘), and use cases. + * Maintainers review requests based on [project tenets](index.md#tenets){target="_blank"}, customers reaction (๐Ÿ‘), and use cases. * **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. - * This helps refine the initial idea with community feedback before a decision is made. + * This helps refine the initial idea with community feedback before a decision is made. * **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. * **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. From a1f939c4391b16b5348513a688b2ee625f868ce0 Mon Sep 17 00:00:00 2001 From: Henrique Graca <999396+hjgraca@users.noreply.github.com> Date: Tue, 11 Feb 2025 10:04:36 +0000 Subject: [PATCH 3/5] Update mkdocs.yml --- mkdocs.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index 9dbf670d..c804a353 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -71,9 +71,12 @@ markdown_extensions: permalink: true toc_depth: 4 - attr_list + - def_list + - pymdownx.tasklist: + custom_checkbox: true - pymdownx.emoji: - emoji_index: !!python/name:materialx.emoji.twemoji - emoji_generator: !!python/name:materialx.emoji.to_svg + emoji_index: !!python/name:material.extensions.emoji.twemoji + emoji_generator: !!python/name:material.extensions.emoji.to_svg - pymdownx.inlinehilite - pymdownx.superfences: custom_fences: From 13fd499b9444279d0ee133f2dc9cfdc3f380be13 Mon Sep 17 00:00:00 2001 From: Henrique Graca <999396+hjgraca@users.noreply.github.com> Date: Tue, 11 Feb 2025 11:26:09 +0000 Subject: [PATCH 4/5] Update roadmap.md --- docs/roadmap.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 7e55e489..871b05db 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -27,18 +27,17 @@ Modernizing our logging capabilities to align with .NET practices and improve de - [ ] Logger buffer implementation - [ ] New .NET-friendly API design (Serilog-like patterns) -- [ ] Correlation ID support via decorator/middleware -- [ ] JMESPath expression support -- [ ] RFC: Documentation for SDK context.Logger vs Powertools Logger differences +- [ ] Filtering and JMESPath expression support +- [ ] Documentation for SDK context.Logger vs Powertools Logger differences #### Metrics V2 Updating metrics implementation to support latest EMF specifications and improve performance. - [ ] Update to latest EMF specifications -- [ ] Breaking changes implementation -- [ ] Performance optimizations -- [ ] API updates +- [ ] Breaking changes implementation for multiple dimensions +- [ ] Add support for default dimensions on ColdStart metric +- [ ] API updates - missing functionality that is present in Python implementation (ie: flush_metrics) ### Security and Production Readiness (P1) @@ -46,9 +45,9 @@ Ensuring enterprise-grade security and compatibility with latest .NET developmen - [ ] .NET 10 support from day one - [ ] Deprecation path for .NET 6 -- [ ] Security and best practices - [ ] Scorecard implementation -- [ ] Security compliance checks +- [ ] Security compliance checks on our pipeline +- [ ] All utilities with end-to-end tests in our pipeline ### Feature Parity and ASP.NET Support (P2) From 1d6b9707b3d50984eb2489ae62f5539d63c4864c Mon Sep 17 00:00:00 2001 From: Henrique Graca <999396+hjgraca@users.noreply.github.com> Date: Tue, 11 Feb 2025 11:29:12 +0000 Subject: [PATCH 5/5] Update roadmap.md --- docs/roadmap.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/roadmap.md b/docs/roadmap.md index 871b05db..e88a50c1 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -14,7 +14,9 @@ Our public roadmap outlines the high level direction we are working towards. We ### Key areas Security and operational excellence take precedence above all else. This means bug fixing, stability, customer's support, and internal compliance may delay one or more key areas below. + **Missing something or want us to prioritize an existing area?** + You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-dotnet/issues?q=is%3Aissue%20state%3Aopen%20label%3Afeature-request){target="_blank"}, leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord. [![Join our Discord](https://dcbadge.vercel.app/api/server/B8zZKbbyET)](https://discord.gg/B8zZKbbyET){target="_blank"}