Skip to content

Commit 983722e

Browse files
committed
docs(roadmap): include observability provider and lambda layer themes before v2
1 parent a9a3f96 commit 983722e

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

docs/roadmap.md

+15-1
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,28 @@ This is our public roadmap that outlines the high level direction we are working
88

99
## Themes
1010

11+
!!! info "Operational Excellence is priority number 1."
12+
1113
Themes are key activities maintainers are focusing on, besides bug reports. These are updated periodically and you can find the latest [under Epics in our public board](https://github.com/orgs/awslabs/projects/51/views/11?query=is%3Aopen+sort%3Aupdated-desc){target="_blank"}.
1214

1315
### Increased end-to-end coverage
1416

15-
We continue to work on increasing end-to-end coverage for all features. Our main challenge is creating a mechanism to periodically test contracts for Lambda Event Sources, since there is no official JSON Schema at the moment.
17+
We continue to work on increasing end-to-end coverage for all features. Our main challenge is testing contracts for Lambda Event Sources (Parser, Event Source Data Classes) due to the lack of an official JSON schema.
1618

1719
Some Lambda Event Sources require clusters (e.g., MSK) leading to additional delays of up to 30m in the end-to-end feedback loop. We need a RFC to start discussing viable options, and whether we should publish JSON Schemas from identified contracts.
1820

21+
### Observability providers
22+
23+
We want to extend Tracer, Metrics, and Logger to support any [observability provider](https://github.com/awslabs/aws-lambda-powertools-python/issues/1433). We need a RFC to define a contract and to identify two most requested observability providers that we can work with as an initial step.
24+
25+
### Lambda Layer in release notes
26+
27+
We want to publish a JSON with a map of region and Lambda Layer ARN as a GitHub Release Note asset.
28+
29+
As of V2, we prioritize Lambda Layers being available before release notes are out. This is due to X86 and ARM64 compilation for smaller binaries and extra speed.
30+
31+
This means we have room to include a JSON map for Lambda Layers and facilitate automation for customers wanting the latest version as soon as it's available.
32+
1933
### Strict typing
2034

2135
We want to enable MyPy strict mode against the code base. We need a RFC to identify most critical areas to start, and do so gradually as to not impact new features and enhancements in parallel.

0 commit comments

Comments
 (0)