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
Copy file name to clipboardExpand all lines: docs/roadmap.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -25,10 +25,10 @@ You can help us prioritize by [upvoting existing feature requests](https://githu
25
25
26
26
This is a roadmap item that we carry forward from 2024 and involves the creation of a new utility for customers to work with REST APIs built on AWS Lambda, and Amazon API Gateway REST and HTTP APIs, Application Load Balancer (ALB), Lambda Function URLs, and VPC Lattice. It's one of the most requested features in terms of feature parity from our customers.
27
27
28
-
You can follow the progress of this feature in the [Event Handler REST milestone](https://github.com/aws-powertools/powertools-lambda-typescript/milestone/17). Below are some of the key macro tasks that we will be working on:
28
+
You can follow the progress of this feature in the [Event Handler REST milestone](https://github.com/aws-powertools/powertools-lambda-typescript/milestone/17){target="_blank"}. Below are some of the key macro tasks that we will be working on:
29
29
30
-
-[x][Explore pros & cons of whether to build atop lean frameworks (e.g., Hono) or from scratch](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2409)
31
-
-[x][RFC to discuss initial thoughts and feasibility for TS/JS ecosystem](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/3500)
30
+
-[x][Explore pros & cons of whether to build atop lean frameworks (e.g., Hono) or from scratch](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2409){target="_blank"}
31
+
-[x][RFC to discuss initial thoughts and feasibility for TS/JS ecosystem](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/3500){target="_blank"}
32
32
-[ ] Support for API Gateway REST API resolver
33
33
-[ ] Support for API Gateway HTTP API resolver
34
34
-[ ] Support for Lambda Function URL resolver
@@ -55,9 +55,9 @@ To close the gap between Powertools for AWS Lambda (Python) and Powertools for A
55
55
56
56
##### Logger
57
57
58
-
-[ ][Ability to buffer logs](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/3410)
59
-
-[ ][Ability to add a correlation ID to logs via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2863)
60
-
-[ ][Ability to refresh debug log sampling rate via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3278)
58
+
-[ ][Ability to buffer logs](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/3410){target="_blank"}
59
+
-[ ][Ability to add a correlation ID to logs via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2863){target="_blank"}
60
+
-[ ][Ability to refresh debug log sampling rate via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3278){target="_blank"}
61
61
62
62
##### Event Handler
63
63
@@ -76,20 +76,20 @@ We will update this roadmap with more details as they become available.
76
76
77
77
To streghten our offering for more advanced customers as well as enterprises, we will be working on a set of activities that will help us better support their needs and practices. These include:
78
78
79
-
-[ ][Publish Lambda layers to GovCloud](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3423)
79
+
-[ ][Publish Lambda layers to GovCloud](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3423){target="_blank"}
80
80
-[ ] Publish China regions
81
-
-[ ][Publish SSM Parameters to lookup Lambda layers ARNs](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3439)
81
+
-[ ][Publish SSM Parameters to lookup Lambda layers ARNs](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3439){target="_blank"}
82
82
-[ ] Improve OSS supply chain posture (Q2) by making sure we're auditing our dependencies for compatible licenses and include NOTICE files in our Lambda layers
83
83
-[ ] Create a new "Advanced Use Cases" section in the docs - to help customers with more complex use cases, such as running Powertools for AWS Lambda in container environments
84
84
-[ ] Set up CI/CD for performance testing
85
85
-[ ] Improve performance of our core utilities
86
-
-[ ][Improve performance overhead of Lambda layers](https://github.com/aws-powertools/powertools-lambda-typescript/issues/1725)
86
+
-[ ][Improve performance overhead of Lambda layers](https://github.com/aws-powertools/powertools-lambda-typescript/issues/1725){target="_blank"}
87
87
88
88
#### Community engagement & new customers (p4)
89
89
90
90
To ensure we are attracting tomorrow's customers as well as new contributors to the project, we will be working on a set of activities that will help us better engage with the community and new customers. These include:
91
91
92
-
-[ ][Create a new "Getting Started" guide in the docs](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2948)
92
+
-[ ][Create a new "Getting Started" guide in the docs](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2948){target="_blank"}
93
93
-[ ] Further improve the "Contributing" & "How to find contributions" pages
94
94
-[ ] Surface contribution opportunities in Discord & other community channels
95
95
-[ ] Improve release notes announcements in Discord & other community channels
0 commit comments