Closed
Description
Summary
The publish_layer.yaml workflow currently has a hardcoded version on the CDK CLI. Given that in #1228 we have recently bumped the version of the actual CDK stack, the fact that this is hardcoded makes it fail as they are not aligned.
Why is this needed?
Because if the two versions are not aligned the workflow might fail, like it happened here, preventing the layers to be published.
Which area does this relate to?
Automation
Solution
Temporarily, as a short term fix that allows us to publish layers, manually bump the version in the workflow to align it with the one used in the layer-publisher folder.
Later, remove the hardcoded version number from the workflow and manage the dependency in the layer-publisher workflow. This work is tracked in #1226.
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Python, Java