aws / aws/chalice

Add an option to overwrite existed lambda functions

Open
#731 4 comments 2 reactions 0 assignees View on GitHub
feature-request
Dominant language
Python
Stars
11.1k
Forks
1k
Avg merge
1d 22h
Merged PRs (30d)
2

Description

If a function already exists in AWS lambda, following error will be raised when running ```chalice deploy```

```
ERROR - While sending your chalice handler code to Lambda to create function
"somefunction", received the following error:

An error occurred (ResourceConflictException) when calling the CreateFunction
operation: Function already exist: somefunction
```

Will it be better if an option is added to enable overwriting existed lambda functions? This is because it is very common to have existed lambda function due to deployment failure or deleting ```deployed.json``` accidentally.

Contributor guide

Open the contributing guide

Research direction

Start with the `chalice deploy` path and the Lambda CreateFunction failure shown in the issue. Determine how an option should handle functions that already exist, including deployments after a failed deploy or a deleted `deployed.json`; done means the option allows the existing Lambda function to be overwritten without the ResourceConflictException.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.