-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
automationThis item relates to automationThis item relates to automationcompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
Description
Summary
The reusable_deploy_layer_stack.yml 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
No response
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Python, Java
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationcompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)