Don't update scheam on deployment to API that already exists

[tayler-kemsley]

Hey folks,

We've got a usecase where the schema stored in our repo is deployed initially, then changed on the fly by users. The problem we're facing is that when we run serverless deploy to push changes, the schema is getting overriden and replaced with that original schema.

Is there a way of supressing the schema changes if the API already exists, but still push other AppSync at the API level?

[bboure]

Hi,

I don't think this is possible. The schema is required by CloudFormation. What is your use-case? How does the schema change and why?

[tayler-kemsley]

Hi, I'd also find this feature very useful. We allow users to edit the schema via an API, which pushes schema changes to AppSync via the SDK, so the schema we have in code and the schema users see becomes out of sync. The result is that deploying new versions always results in downtime while we push all the user changes back into AppSync.