Jeremy Care

@jpignata Any update on this? We are facing the issue right now..

We also ran into that yesterday and had to do the exact same thing. @jpignata it might be a regression on your side

Hey @bboure, thanks for replying quickly. We have the first service, in charge of deploying the API and the schema. ```typescript export const appSyncMain = { name: `api`, authenticationType: 'API_KEY',...

Okay seems that the v2 doesn't support `apiId` anymore. So I believe the plugin doesn't support our use case of AppSync right @bboure?

Should we fork and add our support ourselves or do you want us to do a PR to add this functionality?

 Here's the architecture we have today and would like to have support with. Also considering creating a custom plugin on our project that will...

The workaround we are doing today is to do a depends_on in serverless-compose so we don't have concurrent updates (not ideal this the deployment time is very long now since...

@Hideman85, I think it's a common topic on this repository, so you might find better solutions for your need in previous issues

@bboure Any thoughts on that?

It's important that the schema is not updatable when the APPSync API is referenced and not created by the plugin. We had to talk to AppSync service team to troubleshoot...