Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
dotnet lambda package is not reproducible
See original GitHub issueDescribe the bug
Because dotnet lambda package does not zero out the mtimes of the files in the zip, the zip file itself constantly changes on every build. This means that even rerunning a build of the same exact commit will lead to a cdk diff.
Expected Behavior
dotnet lambda package should produce identical results given identical inputs.
Current Behavior
The original mtimes are preserved, so there is always a diff.
Reproduction Steps
- Run
dotnet lambda package. - Use
cdk deployto deploy a stack with that lambda function. - Run
dotnet lambda packageagain. - Run
cdk diff.
Possible Solution
Set all mtimes to zero (or provide a flag for this).
Additional Information/Context
No response
Targeted .NET platform
.NET Core 3.1
CLI extension version
amazon.lambda.tools 4.0.0 dotnet-lambda
Environment details (OS name and version, etc.)
Debian
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Regardless of whether you want to consider it a bug or a feature request, the problem is that
dotnet lambda packageis currently incompatible with cdk. And it is incompatible because it does not allow for byte-for-byte reproducible builds (hence the issue title).Probably a duplicate of https://github.com/aws/aws-extensions-for-dotnet-cli/issues/195.