serverless-appsync-plugin icon indicating copy to clipboard operation
serverless-appsync-plugin copied to clipboard

After initial deploy of Appsync it wont update

Open Xocix opened this issue 4 years ago • 7 comments

The first time i do command serverless deploy everything works as expected. If i modify the schema or modify existing mappings for response or request they will never be updated when i run command serverless deploy again. Why is this happening, am i doing it wrong?

Serverless version: 1.46.1 Plugin version: 1.1.2

Xocix avatar Jul 06 '19 18:07 Xocix

@Xocix Are you still experiencing this issue?

bboure avatar Dec 13 '19 18:12 bboure

yes, i am facing this issue.

zzramzz avatar Feb 19 '20 05:02 zzramzz

@bboure , is there any fix or workaround for this issue. I have a lot of mutations and queries. It is very difficult to update mapping and attach data sources manually.

Mudassir-23 avatar May 17 '20 07:05 Mudassir-23

@Mudassir-23 I have never faced this issue myself.

It is very difficult to update mapping and attach data sources manually

Have you manipulated your AppSync stack manually? I guess this could be a reason why this issue happens. (Even though I can imagine that the issue happened originally without touching manually?)

One thing you could do is check the CloudFormation events log and try to see what happened.

bboure avatar May 21 '20 06:05 bboure

@bboure I faced this issue without any manipulation to AppSync stack. I just faced this once where I had to update a lot of mutations manually. Post that with next deployments it worked fine. I'm trying to replicate this, will keep you posted if I could identify a pattern for replication.

Mudassir-23 avatar May 22 '20 05:05 Mudassir-23

I have the same issue now, it does not update the schema and the mappingTemplates

joaocostamm avatar Jul 01 '21 09:07 joaocostamm

Just adding a +1 for this issue.

During debugging I sometimes make manual changes to the VTL templates. Then later I run sls deploy --force to reset them back to the codebase. At this time, I find the deploy command appears to succeed but the VTL templates themselves don't get updated. I've also found the same thing when updating the REST data source URL.

Potential Workaround: If I make subtle edits to the resources in my codebase (e.g. change the description of a CF resource, or add a space somewhere into a VTL template), it seems to help either the plugin or AWS itself to detect and process the change.

sc0ttdav3y avatar Sep 24 '21 04:09 sc0ttdav3y