Maintenance: Automate the layer version tracking during the `Make Release` workflow

[sdangol]

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.

[dreamorosi]

Basically right now the maintainer who makes a release needs to: 1/ check the current layer version, 2/ increment the number in their head, and 3/ input it in the workflow - this can be (and has been) error prone.

An alternative to storing a file in the repo could be to use the public SSM Parameter we have and add a step at the beginning of the "update layer in docs" step that fetches the version and increments it by one:

LAYER_VERSION = aws ssm get-parameter --name /aws/service/powertools/typescript/generic/all/latest --region us-east-1
NEW_LAYER_VERSION = $LAYER_VERSION + 1

If we implement this, let's make port it to the Python repository as well if @leandrodamascena is interested.