Open josefaidt opened 2 years ago
reproduced this in my application and observed the inconsistencies in error message provided when exiting early.
Note: In addition to this when adding a custom resource using amplify add custom
and exiting at Provide a name for your custom resource
will result in amplify generating a report with a identifier.
marking as bug
Before opening, please confirm:
How did you install the Amplify CLI?
pnpm
If applicable, what version of Node.js are you using?
v18.7.0
Amplify CLI Version
10.0.0
What operating system are you using?
mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
n/a
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
When exiting out of
add <category>
flows using ctrl+c, the Amplify CLI presents different behaviors between the categories. Some are logging an error and some simply exitExpected behavior
either
Reproduction steps
amplify init -y
amplify add storage
GraphQL schema(s)
Project Identifier
No response
Log output
Additional information
No response