-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Open
Labels
area: integration/cdkIssues related to AWS Cloud Development KitIssues related to AWS Cloud Development Kitaws:lambdaAWS LambdaAWS Lambdastatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I've included a working example of the issue. In the example it will:
- Start the localstack server
- Bootstrap the CDK
- Deploy the nodejs function with a version (this works fine)
- Redeploy the nodejs function with a minor change to the handler. (this will fail)
The output from the example will provide you with all the details of the issue.
2:07:29 AM | UPDATE_FAILED | AWS::Lambda::Alias | FnAliaslive17DB7803 Resource provider operation failed: An error occurred (ResourceConflictException) when calling the CreateAlias operation: Alias already exists: arn:a ws:lambda:us-east-1:000000000000:function:AliasExampleStack-Fn9270CBC0-d1955cf2:live
Expected Behavior
The second deployment should work with the new handler.
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
lambda-alias-error.tgz
docker-compose up --build
Environment
- OS:
- LocalStack:
LocalStack version:
LocalStack Docker image sha:
LocalStack build date:
LocalStack build git hash:Anything else?
No response
Metadata
Metadata
Assignees
Labels
area: integration/cdkIssues related to AWS Cloud Development KitIssues related to AWS Cloud Development Kitaws:lambdaAWS LambdaAWS Lambdastatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report