aws-amplify / aws-amplify/amplify-cli

amplify delete command should show confirmation of which app ID it's going to delete

Open
#10,112 1 comment 0 reactions 0 assignees View on GitHub
feature-request 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?

New category

### Is this related to another service?

_No response_

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

I was trying to get set up with a friend's Amplify environment. In the process, I accidentally created my own Amplicy application in my personal AWS account instance. Once I realized this mistake, I canceled the initialization script partway through. Now I'm trying to delete the created application and resources. Unfortunately, I can't do it from the web UI due to another issue, so I'm trying to do it now via `amplify delete`. I'm running the command from my local copy of their amplify project, and I want to be extra sure that me running the command won't mess up anything in their environment. When you start the command, the only message is:

> Are you sure you want to continue? This CANNOT be undone. (This will delete all the environments of the project from
the cloud and wipe out all the local files created by Amplify CLI) (y/N)

I'm always paranoid of destructive operations, and I'm extra paranoid here, because I don't know if typing `y` will immediately just start the deletion operation. I wish I knew which appId (and just **any** information really) is going to be affected by running the command before I say yes or no

### Describe the solution you'd like

The CLI should display a brief blurb of information describing the Application, Environment, and maybe AWS region that running the command will impact. This will make it so that a user can be confident that they're not about to perform an irreversible operation on something they don't intend.

Better yet, require the command to take an `--appId` as the parameter.

### Describe alternatives you've considered

n/a

### Additional context

I'm a first time user of AWS Amplify, so please let me know if this already exists or if typing `y` gives further verification. Thanks a ton! 😀

### 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

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.