fix(lambda): use of currentVersion
fails deployment after upgrade
#26777
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.0
and version2.88.0
, the hash calculation used to make sure thatfn.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.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license