Open ChadyG opened 1 year ago
Hey @ChadyG :wave: thanks for raising this! I was able to reproduce this using the following steps:
amplify init -y
amplify add api
> GraphQL > choose the "Todo" sample schemaamplify push -y
@primaryKey
to the name
prop
type Todo @model {
id: ID!
name: String! @primaryKey
description: String
}
amplify push -y
, review: https://docs.amplify.aws/cli/graphql/authorization-rules
⠋ Building resource api/13100✅ GraphQL schema compiled successfully.
Edit your schema at /Users/josefai/Documents/projects/aws-amplify/reproductions/13100/amplify/backend/api/13100/schema.graphql or place .graphql files in a directory at /Users/josefai/Documents/projects/aws-amplify/reproductions/13100/amplify/backend/api/13100/schema
Deployment completed.
Deploying api 13100 [ ====------------------------------------ ] 1/9
GraphQLAPITransformerSchema3C… AWS::AppSync::GraphQLSchema UPDATE_COMPLE
Rolled back (2 of 1)
🛑 ["Index: 0 State: {\"deploy\":\"waitingForDeployment\"} Message: Resource is not in the state stackUpdateComplete"]
Marking as a bug and transferring to our API repo for tracking purposes.
I am also getting this error. I've been going around and around on this for days. Amplify is simply unusable.
How did you install the Amplify CLI?
homebrew
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.2.4
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
Previously pushed a test table with default key to our backend. Now pushing full schema with custom primary key on the new table. Using
amplify push -y --allow-destructive-graphql-schema-updates
But this is failing in an odd way. The push operation starts as expected, but once the status output should start, I'm seeing the console get cleared, then no output until the operations finish with errors.Expected behavior
Amplify push succeed or fail as normal
Reproduction steps
Project Identifier
No response
Log output
Additional information
Worked around by dropping the table entirely from the schema, pushing with destructive changes. Then re-adding the table and pushing as normal.
Before submitting, please confirm: