Skip to content

Commit 1980f09

Browse files
heitorlessaheitorlessa
authored
docs(roadmap): april updates (#4181)
* fix(parameters): make cache aware of single vs multiple calls Signed-off-by: heitorlessa <[email protected]> * chore: cleanup, add test for single and nested Signed-off-by: heitorlessa <[email protected]> * chore(ci): add first centralized reusable workflow * docs(roadmap): move bedrock to launched Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): moved parameter/secrets setting to launched Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): add bedrock docs link Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): moved govcloud up top as it's imminent Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): update sigv4 links, observability provider tracer PR Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): move v3 up top due to pydantic v1 EOL Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): add final tasks for govcloud Signed-off-by: heitorlessa <[email protected]> * docs(roadmap): add discord and how customers can help Signed-off-by: heitorlessa <[email protected]> * docs: remove CST as we won't have the bandwidth Signed-off-by: heitorlessa <[email protected]> --------- Signed-off-by: heitorlessa <[email protected]>
1 parent 96095b5 commit 1980f09

File tree

2 files changed

+77
-71
lines changed

2 files changed

+77
-71
lines changed

Diff for: ‎.github/workflows/on_schedule_monthly_roadmap_reminder.yml

-2
Original file line numberDiff line numberDiff line change
@@ -16,5 +16,3 @@ jobs:
1616
uses: aws-powertools/actions/.github/workflows/monthly_roadmap_reminder.yml@fd4575466e5c2ac10703ac16f5aa9fb8890f532a
1717
with:
1818
token: ${{ github.token }}
19-
20-

Diff for: ‎docs/roadmap.md

+77-69
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
1-
<!-- markdownlint-disable MD043 -->
2-
3-
## Overview
1+
<!-- markdownlint-disable MD043 MD041 -->
2+
# Overview
43

54
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.
65

@@ -10,42 +9,60 @@ Our public roadmap outlines the high level direction we are working towards. We
109

1110
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.
1211

13-
### Amazon Bedrock Agent Event Handler
12+
**Missing something or want us to prioritize an existing area?**
1413

15-
Based on [customers](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"} at re:Invent 2023, we will add a new Event Handler resolver to improve authoring and maintenance of Amazon Bedrock Agents.
14+
You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-python/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Afeature-request), leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord.
15+
16+
### Observability providers
17+
18+
We want to extend Tracer, Metrics, and Logger to support any [AWS Lambda certified observability partner](https://go.aws/3HtU6CZ){target="_blank"}, along with OpenTelemetry.
19+
20+
At launch, we will support Datadog since it's [most requested observability provider](https://github.com/aws-powertools/powertools-lambda-python/issues/1433). OpenTelemetry will be a fast follow-up as we need to decide on a stable solution to cold start penalty.
21+
22+
!!! tip "Help us identify which observability providers we should integrate next. Open [feature request](https://github.com/aws-powertools/powertools-lambda-python/issues/new?assignees=&labels=feature-request%2Ctriage&projects=&template=feature_request.yml&title=Feature+request%3A+TITLE){target="_blank"} or by voting `+1` in existing issues"
1623

1724
**Major updates**
1825

19-
* [x] [Event Source Data Classes support](https://github.com/aws-powertools/powertools-lambda-python/pull/3262)
20-
* [x] [Pydantic model _(Parser)_ support](https://github.com/aws-powertools/powertools-lambda-python/pull/3286)
21-
* [x] [MVP Event Handler](https://github.com/aws-powertools/powertools-lambda-python/pull/3285)
22-
* [ ] [New feature documentation](https://github.com/aws-powertools/powertools-lambda-python/pull/3602)
23-
* [ ] Video to walkthrough use cases for anyone new to LLM Agents
24-
* [ ] Launch amplifier (_e.g., What's New, Blog post_)
26+
* [x] [Document how customers can use any provider with Logger](https://docs.powertools.aws.dev/lambda/python/latest/core/logger/#observability-providers)
27+
* [x] [Extend Metrics to add support for any Provider](https://github.com/aws-powertools/powertools-lambda-python/pull/2194)
28+
* [ ] [Extend Tracer to add support for any Provider](https://github.com/aws-powertools/powertools-lambda-python/pull/2342#issuecomment-2061734362)
29+
* [ ] Investigate alternative solution to OpenTelemetry cold start performance
2530

26-
### Setting Parameters and Secrets
31+
### Lambda Layer in GovCloud
2732

28-
As of today, the [Parameters](./utilities/parameters.md){target="_blank"} feature is used to retrieve data, not to create or update existing parameters. Based on community feedback, we plan to enhance Parameters to allow set operations.
33+
We want to investigate security and scaling requirements for these special regions, so they're in sync for every release.
34+
35+
!!! note "Help us prioritize it by reaching out to your AWS representatives or [via email](mailto:[email protected])."
2936

3037
**Major updates**
3138

32-
* [x] [RFC](https://github.com/aws-powertools/powertools-lambda-python/issues/3040)
33-
* [ ] [MVP](https://github.com/aws-powertools/powertools-lambda-python/pull/2858)
39+
* [x] Gather agencies and customers name to prioritize it
40+
* [x] Investigate security requirements for special regions
41+
* [x] Create additional infrastructure for special regions
42+
* [x] AppSec review
43+
* [x] Update CDK Layer construct to include regions
44+
* [x] Distribution sign-off
45+
* [ ] Distribute latest version
46+
* [ ] Update Layer section with new AWS Accounts
3447

35-
### Observability providers
48+
### V3
3649

37-
We want to extend Tracer, Metrics, and Logger to support any [AWS Lambda certified observability partner](https://go.aws/3HtU6CZ){target="_blank"}, along with OpenTelemetry.
50+
We are in the process of planning the roadmap for v3. As always, [our approach](./versioning.md){target="_blank"} includes providing sufficient advance notice, a comprehensive upgrade guide, and minimizing breaking changes to facilitate a smooth transition (e.g., it took ~7 months from v2 to surpass v1 downloads).
3851

39-
At launch, we will support Datadog since it's [most requested observability provider](https://github.com/aws-powertools/powertools-lambda-python/issues/1433). OpenTelemetry will be a fast follow-up as we need to decide on a stable solution to cold start penalty.
52+
For example, these are on our mind but not settled yet until we have a public tracker to discuss what these means in detail.
4053

41-
!!! tip "Help us identify which observability providers we should integrate next. Open [feature request](https://github.com/aws-powertools/powertools-lambda-python/issues/new?assignees=&labels=feature-request%2Ctriage&projects=&template=feature_request.yml&title=Feature+request%3A+TITLE){target="_blank"} or by voting `+1` in existing issues"
54+
* **Parser**: Drop Pydantic v1
55+
* **Parser**: Deserialize Amazon DynamoDB data types automatically (like Event Source Data Classes)
56+
* **Parameters**: Increase default `max_age` for `get_secret`
57+
* **Event Source Data Classes**: Return sane defaults for any property that has `Optional[<type>]` returns
58+
* **Batch**: Stop at first error for Amazon DynamoDB Streams and Amazon Kinesis Data Streams (e.g., `stop_on_failure=True`)
4259

4360
**Major updates**
4461

45-
* [x] [Document how customers can use any provider with Logger](https://docs.powertools.aws.dev/lambda/python/latest/core/logger/#observability-providers)
46-
* [x] [Extend Metrics to add support for any Provider](https://github.com/aws-powertools/powertools-lambda-python/pull/2194)
47-
* [ ] [Extend Tracer to add support for any Provider](https://github.com/aws-powertools/powertools-lambda-python/issues/2030)
48-
* [ ] Investigate alternative solution to OpenTelemetry cold start performance
62+
* [ ] Create an issue to track breaking changes we consider making
63+
* [ ] Create a v3 branch to allow early experimentation
64+
* [ ] Create workflows to allow pre-releases
65+
* [ ] Create a mechanism to keep ideas for breaking change somewhere regardless of v3
4966

5067
### Revamp Event Handler
5168

@@ -63,6 +80,17 @@ Based on customers feedback, we want to provide [middleware authoring support](h
6380
* [x] [MVP for OpenAPI and SwaggerUI](https://github.com/aws-powertools/powertools-lambda-python/pull/3109)
6481
* [ ] [MVP for AppSync Batch invoke and partial failure support](https://github.com/aws-powertools/powertools-lambda-python/pull/1998)
6582

83+
### Authentication (SigV4)
84+
85+
[During customers interview](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"}, we hear that signing requests using [AWS SigV4](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html){target="_blank"} could be easier.
86+
87+
Since JWT is a close second, this new utility would cover higher level functions to sign and verify requests more easily.
88+
89+
**Major updates**
90+
91+
* [x] [Issue to outline challenges](https://github.com/aws-powertools/powertools-lambda-python/issues/2493), alternative solutions and desired experience
92+
* [ ] [MVP for AWS SigV4](https://github.com/aws-powertools/powertools-lambda-python/pull/2435)
93+
6694
### Office hours
6795

6896
We heard from [customers](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"} that Powertools for AWS Lambda and its community can move faster than they are able to catch up. While documentation and release notes take these into account, they notice they don't always know advanced tricks, or what other customers tend to do in similar situations.
@@ -79,17 +107,6 @@ Timezones being tricky, we plan to experiment with an afternoon slot in Central
79107
* [ ] Invite Discord community
80108
* [ ] Update roadmap page with Discord event
81109

82-
### Authentication (SigV4)
83-
84-
[During customers interview](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"}, we hear that signing requests using [AWS SigV4](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html){target="_blank"} could be easier.
85-
86-
Since JWT is a close second, this new utility would cover higher level functions to sign and verify requests more easily.
87-
88-
**Major updates**
89-
90-
* [ ] RFC to outline challenges, alternative solutions and desired experience
91-
* [ ] [MVP for AWS SigV4](https://github.com/aws-powertools/powertools-lambda-python/pull/2435)
92-
93110
### Enhanced operational metrics
94111

95112
[Through customers interview](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"}, [Discord](https://discord.gg/B8zZKbbyET){target="_blank" rel="nofollow"}, and [1:1 customer enablement](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"}, we noticed customers often create the same set of custom operational metrics.
@@ -105,41 +122,6 @@ We want to make this easier by extending certain utilities to accept a `metrics`
105122
* [ ] RFC to outline metrics for Event Handler (_e.g., validation errors_ )
106123
* [ ] RFC to outline metrics for Idempotency (_e.g., cache hit_)
107124

108-
### Lambda Layer in GovCloud and China region
109-
110-
We want to investigate security and scaling requirements for these special regions, so they're in sync for every release.
111-
112-
!!! note "Help us prioritize it by reaching out to your AWS representatives or [via email](mailto:[email protected])."
113-
114-
**Major updates**
115-
116-
* [x] Gather agencies and customers name to prioritize it
117-
* [x] Investigate security requirements for special regions
118-
* [x] Create additional infrastructure for special regions
119-
* [ ] AppSec review
120-
* [ ] Distribution sign-off
121-
* [ ] Update CDK Layer construct to include regions
122-
123-
### V3
124-
125-
We are in the process of planning the roadmap for v3. As always, [our approach](./versioning.md){target="_blank"} includes providing sufficient advance notice, a comprehensive upgrade guide, and minimizing breaking changes to facilitate a smooth transition (e.g., it took ~7 months from v2 to surpass v1 downloads).
126-
127-
For example, these are on our mind but not settled yet until we have a public tracker to discuss what these means in detail.
128-
129-
* **Parser**: Drop Pydantic v1
130-
* **Parser**: Deserialize Amazon DynamoDB data types automatically (like Event Source Data Classes)
131-
* **Parameters**: Increase default `max_age` for `get_secret`
132-
* **Event Source Data Classes**: Return sane defaults for any property that has `Optional[<type>]` returns
133-
* **Upgrade tool**: Consider building a CST (Concrete Syntax Tree) tool to ease certain upgrade actions like `pyupgrade` and `django-upgrade`
134-
* **Batch**: Stop at first error for Amazon DynamoDB Streams and Amazon Kinesis Data Streams (e.g., `stop_on_failure=True`)
135-
136-
**Major updates**
137-
138-
* [ ] Create an issue to track breaking changes we consider making
139-
* [ ] Create a v3 branch to allow early experimentation
140-
* [ ] Create workflows to allow pre-releases
141-
* [ ] Create a mechanism to keep ideas for breaking change somewhere regardless of v3
142-
143125
## Roadmap status definition
144126

145127
<center>
@@ -209,6 +191,32 @@ A: For existing features, you can directly comment on issues. For anything else,
209191

210192
## Launched
211193

194+
### Setting Parameters and Secrets
195+
196+
> [Docs](./utilities/parameters.md#setting-parameters)
197+
198+
As of today, the [Parameters](./utilities/parameters.md){target="_blank"} feature is used to retrieve data, not to create or update existing parameters. Based on community feedback, we plan to enhance Parameters to allow set operations.
199+
200+
**Major updates**
201+
202+
* [x] [RFC](https://github.com/aws-powertools/powertools-lambda-python/issues/3040)
203+
* [x] [MVP](https://github.com/aws-powertools/powertools-lambda-python/pull/2858)
204+
205+
### Amazon Bedrock Agent Event Handler
206+
207+
> [Docs](./core/event_handler/bedrock_agents.md)
208+
209+
Based on [customers](https://github.com/aws-powertools/powertools-lambda-python#connect){target="_blank"} at re:Invent 2023, we will add a new Event Handler resolver to improve authoring and maintenance of Amazon Bedrock Agents.
210+
211+
**Major updates**
212+
213+
* [x] [Event Source Data Classes support](https://github.com/aws-powertools/powertools-lambda-python/pull/3262)
214+
* [x] [Pydantic model _(Parser)_ support](https://github.com/aws-powertools/powertools-lambda-python/pull/3286)
215+
* [x] [MVP Event Handler](https://github.com/aws-powertools/powertools-lambda-python/pull/3285)
216+
* [x] [New feature documentation](https://github.com/aws-powertools/powertools-lambda-python/pull/3602)
217+
* [x] [Video to walkthrough](https://docs.powertools.aws.dev/lambda/python/latest/core/event_handler/bedrock_agents/#video-walkthrough) use cases for anyone new to LLM Agents
218+
* [ ] Launch amplifier (_e.g., What's New, Blog post_)
219+
212220
### Sensitive Data Masking
213221

214222
> [Docs](./utilities/data_masking.md)

0 commit comments

Comments
 (0)