Maintenance: make layer-publisher part of the main npm workspace

[dreamorosi]

Summary

The layer-publisher folder contains the utilities and tests used to publish AWS Lambda Layers for Powertools. When this was developed, it was developed in isolation and with its own dependency tree. Now that the component is somewhat stable, and the dependencies of the main npm workspace has been recently updated, we can bring the folder in the npm workspace so that the dependencies are shared.

Why is this needed?

Because if the two dependency trees are not aligned we risk incurring in the issue described in #1227 every time one of the two trees change. Both trees depend on aws-cdk-lib which has a weekly release cadence so, while the issue is now fixed, it's likely it'll happen again.

Additionally, by having the layer-publisher in the main npm workspace we can decrease the project's footprint on development & CI hosts (because of sharing dependencies) and also simplify some of the workflow that are now disjointed.

Which area does this relate to?

Automation, Other

Solution

No response

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java

[dreamorosi]

While addressing this issue, also try removing the hardcoded CDK version from this workflow.

[dreamorosi]

Also remove this other hardcoded version in this other workflow.

[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.