`amplify pull` is not pulling the changes done manually on the Appsync console to the schema and resolvers
See original GitHub issueDescribe the bug
We used amplify cli to generate the environment and added api, auth and storage. Then we had to manually change the schema in order to add a new pipeline resolver and a new Query field. After we have done the changes. the amplify pull
command is no pulling the changes done on the console.
Pre-Pull and Pos-Pull statuses both showing No Change against Auth, Api and Storage when we definitely have changes against Api.
Amplify CLI Version 4.18.1
To Reproduce
1- generate a new backend using amplify SDK.
2- Add GraphQL API using amplify SDK.
3- Make schema changes manually using AppSync console. (e.g. Add a new field or change existing resolver or add a new pipeline resolver)
4- use amplify pull
command to pull those changes.
Expected behavior The changes made in the schema and resolvers should be pulled down and available locally.
Desktop (please complete the following information):
- OS: Mac
- Node Version: v12.16.3
Additional context
due to this issue, amplify codegen
is also not generating the correct API.swift file. It is not taking the changes done on appsync console into account.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:11 (1 by maintainers)
The docs at that link state: “The amplify pull command operates similar to a git pull, fetching upstream backend environment definition changes from the cloud and updating the local environment to match that definition.” That’s not helpful. Indeed, it may be pulling the environment definition down, but why does that not include manual changes made to the environment? Is there a configuration file of sorts that is a duplicate of what is actually running in AppSync (what you see at the AWS Console), so that making edits at the console diverges the backend configuration from the actual running configuration? I’m not clear on this, but running amplify pull does not bring the resolvers, functions, or schema from the actively running AppSync into the local project. That is certain. I used the AppSync console to create my schema, resolvers, and functions, because 1) it is intuitive and easy to use, and 2) I didn’t know enough about Amplify to realize making changes at that console are not supported. I’ve had those changes in the backend overwritten twice now after upgrading the amplify tool, and it reset my entire schema, functions, and resolvers. After the first amplify upgrade, it lost my backend configuration locally entirely, and this time it overwrote my backend with a very old backend configuration.
I was hoping to find a way to sync the changes I made manually at the AWS AppSync Console back into my project, but it appears that’s not possible, in a straight forward CLI approach at least.
Have the same problem as above. Used the AppSync console to use an existing DynamoDB and create schema for it. When running amplify pull I don’t get the new settings and can’t access my existing db from my app. Why was this issue closed?