aws-amplify / aws-amplify/amplify-cli

Inconsistent status between PUSH and STATUS commands after push fail

Open
#7,805 4 comments 0 reactions 0 assignees View on GitHub
bug p2 platform strategic
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?

_No response_

### Amplify CLI Version

5.0.0

### What operating system are you using?

Mac

### Amplify Categories

auth

### Amplify Commands

push

### Describe the bug

I was facing this issue #7299 too. After the push fail, `amplify status` shows status as no change and `amplify push` shows status as created for the existing resources. On the previous push when upload to s3 failed, resources were created but `amplify push` still shows the resources as new resources.

### Expected behavior

Since the resources were created and just the upload of trigger files failed, it should show status as `update`.

### Reproduction steps

1. Setup Auth with email verification link capability
2. `amplify push`
3. Compare the status with `status` and `push`.

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Log output

```
% amplify status
Current Environment: dev
| Category | Resource name | Operation | Provider plugin |
| -------- | ------------------------------------- | --------- | ----------------- |
| Function | auth136309e925c409e925c4CustomMessage | No Change | awscloudformation |
| Auth | auth136309e925c409e925c4 | No Change | awscloudformation |

% amplify push
✔ Successfully pulled backend environment dev from the cloud.
Current Environment: dev
| Category | Resource name | Operation | Provider plugin |
| -------- | ------------------------------------- | --------- | ----------------- |
| Function | auth136309e925c409e925c4CustomMessage | Create | awscloudformation |
| Auth | auth136309e925c409e925c4 | Create | awscloudformation |
? Are you sure you want to continue? Yes
```

### Additional information

_No response_

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.