Skip to content

Remote changes to Lambda code do not trigger update #906

Open

Description

This is with a TypeScript project using only aws resources, no awsx ones. Pulumi v1.13.0, @pulumi/aws@1.27.0.

Steps:

  1. Make code changes to a Lambda function in the AWS console
  2. Run pulumi up -r

At this point in the "details" it will show that there are differences with the Lambda function, such as lastModified, sourceCodeHash, and sourceCodeSize. Yet the summary says 188 unchanged and if I proceed with the up the remote Lambda changes are not reverted.

For example during the up it shows sourceCodeSize: 2762 => 2764. The state at that time (before proceeding) indeed shows 2762. Proceeding, then checking the state again, the state has updated to 2764, but the remote code is unchanged even though it doesn't match the local code.

During imports of existing Lambdas I recall having to comment out the code key for the Lambda in Pulumi otherwise it would give the import will fail due to it not matching error. I'm guessing that might be related? At the time I figured it was some sort of import limitation.

The only way to get the remote code to update is to update the local code. At that point a change is detected and the local code is successfully pushed to remote.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

area/refreshawaiting-upstreamThe issue cannot be resolved without action in another repository (may be owned by Pulumi).blockedThe issue cannot be resolved without 3rd party action.kind/bugSome behavior is incorrect or out of specservice/lambdaLambda issuessize/SEstimated effort to complete (1-2 days).

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions