aws-amplify / aws-amplify/amplify-cli

Verbose option for CLI

Open
#7,509 9 comments 10 reactions 0 assignees View on GitHub
feature-request ops-errors p3 platform
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

16.3.0

### Amplify CLI Version

4.51.4

### What operating system are you using?

Wdinows

### Amplify Categories

Not applicable

### Amplify Commands

Not applicable

### Describe the bug

https://github.com/aws-amplify/amplify-cli/issues/501 was locked, but was never fully resolved (see followup discussion on the issue).

In my particular case, I'm facing this error:

```
UPDATE_FAILED GraphQLSchema AWS::AppSync::GraphQLSchema Sat Jun 12 2021 10:42:30 GMT-0700 (Pacific Daylight Time) The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: ; S3 Extended Request ID: ; Proxy: null)
```

and I'm having to manually debug into the CLI to see what the request is actually trying to do in order to have a hint of how to fix it.

### Expected behavior

There should be a --verbose option on the CLI

### Reproduction steps

N/A

### GraphQL schema(s)

_No response_

### Log output

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue names only the Amplify CLI and provides no files or tests, so start by locating the CLI entry point and its existing logging behavior. Define completion as a documented --verbose option that exposes useful diagnostic details for failures such as the reported AppSync and S3 error, then verify it against the CLI help and a reproduced failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cli
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.