Appsync js pipeline resolver functions

[theyuv]

Amplify CLI Version

14.0.0

Question

I have written a custom mutation in my schema.graphql

I couldn't find a way to write a series of appsync js pipeline functions for this mutation on my local computer so I used the Appsync console to generate the appsync js functions and added them to the custom mutation's pipeline.

Sometimes, when I run amplify push, the pipeline I built via the console is preserved.
Other times, it is removed and replaced with the req and res vtl resolver that amplify generates.

1. What causes the console pipeline to be overridden on certain pushes?
2. Is there a simple way to define the pipeline on my local computer so that it can be guaranteed to persist after amplify push?

[pahud]

Hi @theyuv,

Thank you for your question! This is actually expected behavior by design.

Why console changes get overwritten:

The Amplify CLI manages your GraphQL API as Infrastructure-as-Code. When you run amplify push, it regenerates resolvers based on your local schema.graphql and deploys them. Changes made directly in the AppSync Console are not tracked by the CLI and will be overwritten when the API category detects changes.

The "sometimes preserved" behavior you're seeing likely occurs when Amplify doesn't detect any changes in your API category - in those cases, it may skip regeneration. But any schema modification will trigger a full resolver rebuild.