-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify deleted my resolvers and now my stack is stuck in UPDATE_ROLLBACK_FAILED #2157
Comments
As others have reported, using the appsync console to create (dummy) resolvers allowed me to then "continue update rollback" successfully, and my stack is now in a usable |
saved my day, thank you. |
@cunneen I am having a similar issue! After major changes in my graphQL schema and some layer. Can you please describe how you create "dummy" resolvers? Thanks a lot!🙏 |
This saved me as well. I was changing a schema model in my Amplify Flutter app and some resolvers disappeared. Specifically, I was trying to allow public subscriptions. Could not force the stack to rollback even when skipping resources. The process to fix it is:
|
Sorry @8maxxam8 for the delay in responding, and thanks @BradVidler for sharing his steps. From memory, my process was very similar but we weren't using subscriptions, and I didn't need to define any subscriptions in the graphQL schema. I think my process was probably not very efficient, but here's how I did it.
|
@BradVidler @cunneen Thanks a lot for your help! This was indeed solving the problem I was facing!👍 |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16
Amplify CLI Version
10.8.1
What operating system are you using?
Amplify CI/CD (amazon linux)
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made before the issue described was encountered. I've since attempted (unsuccessfully so far) to manually attach resolvers via the appsync console to rectify the issue.
Describe the bug
After a couple of failed
amplify pushes
, reverting my failed changes and re-pushing the last successfulamplify push
resulted in my stack having anUPDATE_ROLLBACK_FAILED
state, because somehow the (generated) appsync resolvers are now missing.How I got here
In case it helps explain how this happened, what I was trying to do (in our non-production stack) was to modify four existing appsync
@key
s (i.e. dynamodb GSIs) in our graphql schema, with the eventual goal of adding extra fields to the sortkeys.Understanding that I'd need to delete and then re-create the GSIs, I commented out the
@key
statements , then tried toamplify push
(via CI/CD),i.e.:
... then
amplify push
, but ... oops (my bad), I'd missed a reference thebyLogParentID
key/query, broken the schema and so the push failed with this message:So, I fixed the schema and tried to push again:
... and then
amplify push ...
.But no... this time I encountered
Cannot perform more than one GSI creation or deletion in a single update
:So I edited
cli.json
to enable theenableIterativeGsiUpdates
feature and tried anotheramplify push
. Only to get the same error (!):"Maybe it's a sequencing issue" I thought, reasoning that perhaps the
enableIterativeGsiUpdates
feature needed to be enabled and pushed separately before attempting to change the GSIs.this guy seemed to come to a similar conclusion and said that it worked for him.
So at this point, I'm adding the GSIs back temporarily so I can then try to remove them again before adding them back again. Obviously.
So I tried to "revert" all of the schema.graphql schema changes (which, since the previous deployments had failed, should result in no Appsync changes at all, right? RIGHT?)
WRONG.
No resolver found
, apparently. When simply re-pushing my last successful push WITH NO CHANGES (other than the feature flag).Expected behavior
"Insanity is doing the same thing over and over and expecting different results".
I expected that pushing the exact same graphql schema that had worked before, would work again.
Reproduction steps
Please see the "describe the bug" section above.
Project Identifier
Running the provided command doesn't give a project identifier, nor does it seem to send a zip:
Log output
the "push"-es were all performed within amplify CI/CD so that's where the logs are;
region is
ap-southeast-2
amplify app ID is
d31ul62nbvaagu
amplify app environment is
dev
the build numbers referred to in the "describe the bug" section are: 1868 through to 1871.
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: