fix(lambda): use of currentVersion fails deployment after upgrade#26777
Merged
mergify[bot] merged 3 commits intomainfrom Aug 17, 2023
Merged
fix(lambda): use of currentVersion fails deployment after upgrade#26777mergify[bot] merged 3 commits intomainfrom
currentVersion fails deployment after upgrade#26777mergify[bot] merged 3 commits intomainfrom
Conversation
Between version `2.87.0` and version `2.88.0`, the hash calculation used to make sure that `fn.currentVersion` is automatically updated when a new version of the Lambda Function is deployed changed. This causes a creation of a new Version upon upgrading CDK, but that new Version creation will fail because the underlying Function hasn't changed. The change was due to property ordering used in calculating a unique hash for the Function configuration. This change restores the property ordering to the pre-2.88.0 behavior. Fixes #26739.
currentVersion fails on upgradecurrentVersion fails deployment after upgrade
otaviomacedo
approved these changes
Aug 17, 2023
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Between version
2.87.0and version2.88.0, the hash calculation used to make sure thatfn.currentVersionis automatically updated when a new version of the Lambda Function is deployed changed.This causes a creation of a new Version upon upgrading CDK, but that new Version creation will fail because the underlying Function hasn't changed.
The change was due to property ordering used in calculating a unique hash for the Function configuration.
This change restores the property ordering to the pre-2.88.0 behavior.
Fixes #26739.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license