title: Modifying resolvers in AWS Amplify with RDS backend
body: <p>When using AWS Amplify with a dynamodb backend, it's possible to update the AppSync schema and resolvers by modifying the files locally and then executing <code>amplify push</code>.</p>
  
  <p>I'm using RDS (added it with <code>amplify api add-graphql-datasource</code> as described in the documentation). Queries and resolvers are setup in AppSync automatically. When I update the Aurora RDS schema, I run <code>amplify api add-graphql-datasource</code> again to update queries and resolvers.</p>
  
  <p><em>But how do I add new queries/mutations and bind them to new resolvers (defined in <code>vtl</code> files on localhost), using the amplify CLI?</em> </p>
  
  <p>I figured out how to do it by using the AppSync Web console. I modify the schema and create resolvers in AppSync, then use <code>amplify codegen</code> to update <code>App.ts</code>, <code>queries.ts</code>, etc. However, this approach is bad for at least two reasons. </p>
  
  <ol>
  <li>When working with multiple environments, changes to each environment has to be done manually via the AppSync console, which is difficult for larger projects. </li>
  <li><code>amplify codegen</code> doesn't update the <code>schema.graphql</code> file on localhost.</li>
  <li>Executing <code>amplify push</code> after making changes to AppSync over uses the schema defined on localhost and overwrites the schema defined in the AppSync console.</li>
  <li>Custom resolvers in <code>app/amplify/backend/&lt;backend_name&gt;/resolvers</code> are not synchronized with AppSync</li>
  <li>the stack file is not updated automatically. </li>
  </ol>
  
  <p><strong>Am I going about this the wrong way? Is there a better way of updating schema/resolvers using amplify CLI when using and RDS backend?</strong> </p>
  
  <p>Thank you!</p>