Maintenance: create mechanism to auto publish the layer version for every release

[rubenfonseca]

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

[rubenfonseca]

This was released in v2 🎈

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.