aws-amplify / aws-amplify/amplify-cli

deploy not show statement

Open
#13,419 3 comments 0 reactions 0 assignees View on GitHub
feature-request platform-push
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

npm

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

_No response_

### Amplify CLI Version

isMemberActive

### 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.

no

### Describe the bug

1.After upgrading to the new Amplify version, we can't see any statement after deployment.It just stop and show the Session Identifier. The weird part is that after I get the Session Identifier: fb2a6253-5f5f-4d87-a141-ff22002b85ee, I still see it deploying in the AWS console.We need to go to the S3 bucket to delete the deployment-state.json file for the next deployment otherwise we will get A deployment is in progress error.Screenshot 2023-11-20 at 3 47 54 pm
Screenshot 2023-11-20 at 3 35 37 pm

### Expected behavior

I think 1. it should display a statement indicating whether the deployment is successful or not, and it needs to update the status upon completion.

### Reproduction steps

1.change code
2.amplify init
3. amplify push

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported flow with `amplify init` followed by `amplify push`, and observe the deployment output after the Session Identifier appears. Investigate how the CLI handles `deployment-state.json` and reports completion, then verify that a deployment finishing in the AWS console produces a final success or failure status without requiring manual S3 cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cli, cloud
Issue type
Bug
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.