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
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)layersItems related to the Lambda Layers pipeline
Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered:
am29d
added
triage
This item has not been triaged by a maintainer, please wait
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
labels
Apr 9, 2024
am29d
added
confirmed
The scope is clear, ready for implementation
layers
Items related to the Lambda Layers pipeline
and removed
triage
This item has not been triaged by a maintainer, please wait
labels
Apr 9, 2024
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)layersItems related to the Lambda Layers pipeline
Summary
We need to add the new v2 layer to AWS Lambda console.
Why is this needed?
So customers can use the new v2 version layer in the console.
Which area does this relate to?
No response
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: