Maintenance: update layers workflow to properly manage artifacts

[dreamorosi]

Summary

After updating the github/upload-artifact action we need to make changes to the workflow that deploys the Lambda Layers so that it handles the artifact used to identify the layer ARN properly.

In order to add the ARN to the docs we upload an GitHub artifact containing a text file. We do this both in the beta and prod workflow.

Why is this needed?

In a previous version of the GH Action artifacts were treated as mutable, but in this version are immutable so we need to explicitly configure the action to overwrite the previous version since by the time the production workflow runs there's already an artifact created by the beta run.

Which area does this relate to?

Automation

Solution

See action migration steps

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.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.