Fixed random manifest names causing zip package hash refresh on every build #163
Conversation
This file contains 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
…ash differ on every build
|
Interesting, I didn't realize the name of the manifest file was being put in the deps.json file. Nice find. |
|
This PR was shipped as part of Amazon.Lambda.Tools 5.0.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
#162
Description of changes:
I changed use of temporary filename for layer manifest to be directory name instead. All layers of the project will have their filename built from layer name and version number, located under the new temp directory. This stops hash of zip package to change across executions of package-ci and deploy-serverless commands when no other content changes are introduced.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.