Benoît Bouré

@MarcusJones There are 2 ways to use Direct Lambda currently. 1) set `defaultMappingTemplates.request` and/or `defaultMappingTemplates.response` to false. In this case, it will apply to all lambda resolvers that do not...

Thank you @dodgeblaster The doc definitely needs some refactoring and clarification. I'll try to find some time to do that. In the meantime, I'll add this one.

It should work. Can you also share your VTL template where you are using substitution?

@mihaiblaga89 @mim-Armand anyone knows how `@auth` is working? I haven't tested yet. Has it been integrated directly into AppSync? I cannot find anything in the doc. Only about `aws_auth`, here:...

@mihaiblaga89 Thanks @mihaiblaga89. I know about `@aws_auth` but I thought you guys were talking about `@auth` (like [here](https://aws-amplify.github.io/docs/cli/graphql#auth)) and seemed to say that it was working as well? About GraphQL...

Hi @ChristopherGillis Unfortunately, we are stuck to that version due to some incompatibility with newer versions. I'd have to see if and how we can upgrade in v1. v2 of...

@giraudvalentin Could you please elaborate? What kind of errors are you getting? What do the Lambdas do? ie: do they call AppSync endpoints? Like any other sls framework plugin, this...

There is no way to handle this in the resolver template. It's an error that AppSync throws even before your resolver is called. Apart from using separate stacks I can...

Thank you @AndreasAugustin This will be supported in v2 [See documentation](https://github.com/sid88in/serverless-appsync-plugin/blob/alpha/doc/commands.md#flush-cache)

Got it! I have not used that feature yet, but if I'm not mistaken, this is fully controlled on the VTL level as you mentioned. You already have to write...