aws-amplify / aws-amplify/amplify-cli
Can't push app with deleted table
- 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
14.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.
Deleted a table in DynamoDB manualy from the AWS console
### Describe the bug
I made an error when pushing branches. I'm on amplify gen 1.
I have 2 git branches where I worked on features. On one branch I created a model in graphql called 'AppSubscription' and pushed to with cli. Then I switched to another branch where I don't have this model/table and tried to push and it wouldn't let me so I deleted the database table from dynamoDB console. after that amplify push didn't work from either branch.
I'm getting this error: 'Resource is not in the state stackUpdateComplete'
And in Amplify stack for this env I see this error: Embedded stack arn:aws:cloudformation[...] was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to create: [AppSubscription].
This remained in UPDATE_ROLLBACK_IN_PROGRESS, it didn't finish the rollback
1. how can I fix this UPDATE_ROLLBACK_IN_PROGRESS so I can push again?
2. how do I fix my initial problem with pushing and I have a deleted database table?
### Expected behavior
I want to do 'amplify push' without any errors
### Reproduction steps
1. have master branch in git project
2. create another branch and create new model and add some data in the table
3. switch back to 1st branch and try to push
4. delete the database table from dynamodb console
5. try to push again (from either branch)
### 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
Research direction
No repository files or tests are identified. Start by reproducing the reported branch-switching and amplify push sequence with the deleted DynamoDB AppSubscription table, then inspect the resulting CloudFormation rollback state. Done means the rollback completes and amplify push works without the stackUpdateComplete error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, typescript
- Domain
- api, cli, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100