Skip to content

Conversation

@aarsilv
Copy link

@aarsilv aarsilv commented Aug 12, 2022

This PR adds a new option, --no-handler-update which omits updating the handler on Lambda.
The use case that prompted this PR is we deploy using Claudia, but have a Datadog layer. Thus Claudia's validation needs to use one handler, lib/lambda.handler, while the Lambda configuration needs to point the the Datadog wrapper handler, /opt/nodejs/node_modules/datadog-lambda-js/handler.handler. With this new command line argument we are able to satisfy the above with

claudia update --handler="lib/lambda.handler" --no-handler-update

While testing, I also discovered that the AWS API returns State with a capital "S", while Claudia was looking for lower-case. I adjusted this to match the response so that existing tests passed instead of failed.
Should fix: #226

* add no-handler-update option to omit updating the handler on lambda

* get rid of extra newline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ResourceConflictException: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:

1 participant