-
Notifications
You must be signed in to change notification settings - Fork 168
Closed
Labels
automationThis item relates to automationThis item relates to automationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Description
Summary
Currently, we have to manually track the Layer version number and pass the correct version when running the Make Release
workflow. This could be automated to improve the workflow.
Why is this needed?
This would reduce manual interventions and manual tracking of the layer version and make the process more efficienct
Which area does this relate to?
Automation
Solution
We could simply have a file which contains the layer number which gets incremented when updating the docs arn
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- 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.
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Type
Projects
Status
Coming soon