Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't deploy -- CodeSHA256 is different from current CodeSHA256 in $LATEST #22

Open
jonclegg opened this issue Mar 2, 2021 · 1 comment
Open

Can't deploy -- CodeSHA256 is different from current CodeSHA256 in $LATEST #22

jonclegg opened this issue Mar 2, 2021 · 1 comment

Comments

@jonclegg
Copy link

jonclegg commented Mar 2, 2021

An error occurred: Hello2LambdaVersionSd9LQvg8OLh7YEGXmSYtVoyTp8mzeUdOSyjvdQEsUVs - CodeSHA256 (47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=) is different from current CodeSHA256 in $LATEST (CYFRk/+PE9UJqVlJMbTXIal842HlqNXMUFPLj+aA680=). Please try again with the CodeSHA256 in $LATEST. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 6e67f672-a41a-4ad1-971e-e02541daa4d4; Proxy: null).

Any idea?
@Sandarr95
Copy link
Contributor

I resolved this by setting versionFunctions: false in the provider. We didn't use it at all so it was no problem for us. It's documented what it does here:
https://www.serverless.com/framework/docs/providers/aws/guide/functions#versioning-deployed-functions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonclegg @Sandarr95