Provide a verbose option to see reason for a failure

Is your feature request related to a problem? Please describe. The CLI sometimes displays an error and does not give enough information why. For example, just the phrase “Access Denied”

➜  directory-on-tap git:(master) ✗ amplify push --verbose
| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Auth     | dotauthdev    | Delete    | awscloudformation |
? Are you sure you want to continue? true
✖ An error occurred when pushing the resources to the cloud

Access Denied

or

✖ An error occurred when pushing the resources to the cloud

Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

Describe the solution you’d like I would like an option --verbose and -v which would display the operations which the CLI is performing on the server. With that information, I can diagnose what is the problem and then make changes to the CloudFormation document or User Policy.

Describe alternatives you’ve considered I’ve tried to guess what is wrong, but it’s a frustrating (and unsuccessful in my case) way of understanding what is going wrong.

[rajeshrthl]

I’ve got this same issue. Is there no way to see verbose error message when running amplify commands? Adding a flag like --verbose would be greatly helpful when debugging issues.

[flyandi]

Is there any progress here… this is not useful: