You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I've read the serverless framework is designed to produce deterministic builds, but this is not happening on my project with the dashboard plugin enabled. Each deploy ends up releasing a new Lambda version even if there were no code changes.
From diffing the build zips, it appears the only change is the "deploymentUid" parameter in the generated entrypoint file, this is regenerated on every build.
I'm wondering if this could perhaps be moved to an environment variable rather than hardcoded so the builds can be deterministic and we can avoid unnecessary updates.
The text was updated successfully, but these errors were encountered:
@jonmast thanks for reporting. Yes this is a known issue.
In future we plan to replace Serverless Dashbaord with the Serverless Console where instrumentation approach is way less intrusive. Be sure to check it out, and please report to the support features you miss the most at this point
From what I've read the serverless framework is designed to produce deterministic builds, but this is not happening on my project with the dashboard plugin enabled. Each deploy ends up releasing a new Lambda version even if there were no code changes.
From diffing the build zips, it appears the only change is the "deploymentUid" parameter in the generated entrypoint file, this is regenerated on every build.
I'm wondering if this could perhaps be moved to an environment variable rather than hardcoded so the builds can be deterministic and we can avoid unnecessary updates.
The text was updated successfully, but these errors were encountered: