Skip to content

Commit 8e15245

Browse files
dreamorosidreamorosi
committed
chore: updated disclaimer
1 parent 89f9720 commit 8e15245

File tree

2 files changed

+14
-17
lines changed

2 files changed

+14
-17
lines changed

‎docs/roadmap.md

+12-15
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,7 @@ Our public roadmap outlines the high level direction we are working towards. We
1515

1616
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.
1717

18-
**Missing something or want us to prioritize an existing area?**
19-
20-
You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-typescript/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc++label%3Atype%2Ffeature-request+), leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord.
21-
22-
[![Join our Discord](https://dcbadge.vercel.app/api/server/B8zZKbbyET)](https://discord.gg/B8zZKbbyET){target="_blank"}
18+
!!! info "We may choose to reprioritize or defer items based on customer feedback, security, and operational impacts, and business value."
2319

2420
#### Event Handler REST (p0)
2521

@@ -43,13 +39,7 @@ You can follow the progress of this feature in the [Event Handler REST milestone
4339
- [ ] Support for injecting request details _(consider not doing globals like Python legacy)_
4440
- [ ] Support for Router _(multi-file routes)_
4541

46-
#### Service Team co-launches (p1)
47-
48-
This is a catch-all roadmap item that stands in for activities that the team will be doing to support the launch of new features. Powertools for AWS continued partnership with AWS Service Teams involves the team working with product teams from the earliest stages of design to ensure that features are built by working backwards from the customer.
49-
50-
We will announce these features as they are launched and will update this roadmap with more details as they become available.
51-
52-
#### Feature parity (p2)
42+
#### Feature parity (p1)
5343

5444
To close the gap between Powertools for AWS Lambda (Python) and Powertools for AWS Lambda (TypeScript), we will focus our efforts on adding targeted features that are currently missing from the TypeScript version. These include (but are not limited to):
5545

@@ -58,6 +48,7 @@ To close the gap between Powertools for AWS Lambda (Python) and Powertools for A
5848
- [ ] [Ability to buffer logs](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/3410){target="_blank"}
5949
- [ ] [Ability to add a correlation ID to logs via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/2863){target="_blank"}
6050
- [ ] [Ability to refresh debug log sampling rate via decorator/middleware](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3278){target="_blank"}
51+
- [ ] [Ability to pretty print stack traces](https://github.com/aws-powertools/powertools-lambda-typescript/issues/1362){target="_blank"}
6152

6253
##### Event Handler
6354

@@ -72,20 +63,20 @@ For the Validation utility, we'll experiment with a community-driven approach to
7263

7364
We will update this roadmap with more details as they become available.
7465

75-
#### Governance & Advanced Use Cases (p3)
66+
#### Governance & Advanced Use Cases (p2)
7667

7768
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:
7869

7970
- [ ] [Publish Lambda layers to GovCloud](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3423){target="_blank"}
80-
- [ ] Publish Layers to China regions
71+
- [ ] Publish Lambda layers to China regions
8172
- [ ] [Publish SSM Parameters to lookup Lambda layers ARNs](https://github.com/aws-powertools/powertools-lambda-typescript/issues/3439){target="_blank"}
8273
- [ ] 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
8374
- [ ] 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
8475
- [ ] Set up CI/CD for performance testing
8576
- [ ] Improve performance of our core utilities
8677
- [ ] [Improve performance overhead of Lambda layers](https://github.com/aws-powertools/powertools-lambda-typescript/issues/1725){target="_blank"}
8778

88-
#### Community engagement & new customers (p4)
79+
#### Community engagement & new customers (p3)
8980

9081
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:
9182

@@ -95,6 +86,12 @@ To ensure we are attracting tomorrow's customers as well as new contributors to
9586
- [ ] Improve release notes announcements in Discord & other community channels
9687
- [ ] We will also attempt to create a community-developed new utility (see [Validation](#validation) above)
9788

89+
### Missing something?
90+
91+
You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-typescript/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc++label%3Atype%2Ffeature-request+), leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord.
92+
93+
[![Join our Discord](https://dcbadge.vercel.app/api/server/B8zZKbbyET)](https://discord.gg/B8zZKbbyET){target="_blank"}
94+
9895
### Roadmap status definition
9996

10097
<center>

‎docs/upgrade.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ V2 is focused on official support for ESM (ECMAScript modules). We've made other
2222
| **ESM support** | Added ESM support via dual CommonJS and ESM bundling, enabling top-level `await` and tree-shaking. | - |
2323
| **Middy.js** | Updated import path for Middy.js middlewares to leverage subpath exports - i.e. `@aws-lambda-powertools/tracer/middleware`. | Yes |
2424
| **Types imports** | Updated import path for TypeScript types to leverage subpath exports - i.e. `@aws-lambda-powertools/logger/types`. | Yes |
25-
| **Logger** | Changed [log sampling](./core/logger.md#sampling-logs) to dynamically switch log level to `DEBUG` on a percentage of requests. | - |
25+
| **Logger** | Changed [log sampling](./core/logger.md#sampling-debug-logs) to dynamically switch log level to `DEBUG` on a percentage of requests. | - |
2626
| **Logger** | Updated [custom log formatter](#custom-log-formatter) to include standard as well as persistent keys. | Yes |
2727
| **Logger** | Removed `ContextExamples` from `@aws-lambda-powertools/commons` package. | Yes |
2828
| **Logger and Tracer** | Removed deprecated `createLogger` and `createTracer` helper functions in favor of direct instantiation. | Yes |
@@ -305,7 +305,7 @@ In v2, you have more control over **standard** (`attributes`) and [**custom keys
305305
export { MyCompanyLogFormatter };
306306
```
307307

308-
1. This new argument contains all [your custom keys](./core/logger.md#appending-persistent-additional-log-keys-and-values).
308+
1. This new argument contains all [your custom keys](./core/logger.md#appending-additional-keys).
309309
2. `LogItem` is the new return object instead of a plain object.
310310
3. If you prefer adding at the initialization, use: <br/><br/> **`LogItem({persistentAttributes: additionalLogAttributes, attributes: baseAttributes})`**
311311

0 commit comments

Comments
 (0)