aws-amplify / aws-amplify/amplify-cli

Remove lambda functions from an API gateway on `amplify remove function`

Open
#10,934 1 comment 1 reaction 0 assignees View on GitHub
feature-request functions p4 platform
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### Is this feature request related to a new or existing Amplify category?

function

### Is this related to another service?

_No response_

### Describe the feature you'd like to request

Right now, ```amplify remove function``` is not possible if the function connected to an API Gateway route (yielding the error: "Resource cannot be removed because it has a dependency on another resource, Dependency: API Gateway")

I would like that ```amplify remove function``` can remove functions even though they have dependencies, so that in this case, it also removes the associated API route.

### Describe the solution you'd like

I would like that ```amplify remove function``` can remove functions even though they have dependencies, so that in this case, it also removes the associated API route.

### Describe alternatives you've considered

-

### Additional context

_No response_

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request

### Would this feature include a breaking change?

- [ ] ⚠️ This feature might incur a breaking change

Contributor guide

Open the contributing guide

Research direction

Start by tracing the `amplify remove function` command and the dependency error raised when the function is connected to an API Gateway route. Done means the function can be removed without the dependency error and its associated API route is also removed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.