amplify delete errors when project has been deleted from the AWS Console #11486
Description
Before opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- I have removed any sensitive information from my code snippets and submission.
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.5.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Yes, removed the Amplify app on console
Amplify Categories
Not applicable
Amplify Commands
delete
Describe the bug
Previously when a running amplify delete on a application where the amplify app has been deleted on AWS console, the CLI would remove the amplify folder after checking for stacks and application.
In the newer version of Amplify CLI, the application does the following
-> amplify delete
? 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) Yes
⠋ Deleting resources from the cloud. This will take a few minutes.
Deleting env: abc.
Deleting env: dev.
⠸ Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
⠦ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
⠧ Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
⠸ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
✖ Project delete failed.
🛑 Project delete failed.
App <App ID> not found.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: 8e866bc3-263b-4215-bbea-6b251721c48a
✔ An unexpected error has occurred, opt in to send an error report to AWS Amplify with non-sensitive project configuration files. Confirm (y/N) · no
The application recognizes the deleted app but fails to clean up.
on CLI version 10.0.0
amplify delete
? 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) Yes
- Deleting resources from the cloud. This will take a few minutes.
Deleting env: dev.
| Deleting resources from the cloud. This will take a few minutes.Unable to remove env: dev because deployment bucket amplify-testfullamp-dev-92940-deployment does not exist or has been deleted.
- Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
/ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
√ Project already deleted in the cloud.
Project deleted locally.
Expected behavior
Remove amplify folder if not present and not invoke diagnose when not needed.
Reproduction steps
- amplify init
- delete app on console
- amplify delete
GraphQL schema(s)
Details
# Put schemas below this line
Project Identifier
8e866bc3-263b-4215-bbea-6b251721c48a
Log output
Details
# Put your logs below this line
Additional information
No response