Closed
Description
Summary
Right now, everytime we craft a new release, we have to wait for the Layer Pipeline to finish and manually update/re-generate the documentation to update the Layer ARN version.
We should automate this as part of our release pipeline.
Why is this needed?
In order to reduce maintenance overhead.
Which area does this relate to?
Automation
Solution
The CDK Layer Pipeline already outputs the LayerVersionArn for each region. We can leverage this to automate the replacement of the version in our docs.
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript