Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`amplify push` not to override specific resolvers
See original GitHub issue** Which Category is your question related to? ** API
** What AWS Services are you utilizing? ** AppSync
** Provide additional details e.g. code snippets **
For example, I added manually a global secondary index to a dynamoDB table and set a resolver to scan against it. Now, whenever I update my schema locally and issue amplify push the resolver is overwritten and loses all manually set instructions.
Is there any way to preserve the manually changed resolvers?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, you can do this using the
‘amplify push —no-gql-overridecommand.This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server
*-helpchannels for those types of questions.