Skip to content

Lambda deploy : call to update_configuration_function is made before lambda update status is ready #711

@roamdam

Description

@roamdam

Problem

It seems that the application of lambda states to all functions, including zip-file based lambdas, prevents from deploying as previously with lambda deploy. Several lambdas that I was able to deploy perfectly last week do not deploy now.

Error

The error I'm getting is the following

botocore.errorfactory.ResourceConflictException: An error occurred (ResourceConflictException) when calling the UpdateFunctionConfiguration operation: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:eu-west-3:xxx:function:my-lambda

Observations

It seems that right after calling the client.update_function_code method, the LastUpdateStatus from the lambda's configuration stays at InProgress, thus the subsequent call to client.update_function_configuration is refused by the API.

I've tried adding a simple time.sleep(120) right after the call to client.update_function_code, and it seems to work : after waiting the value of LastUpdateStatus goes back to Successful, and the deployment goes fine afterwards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions