Benoît Bouré

> is it easy to backport to v1? it should be easy enough. > and is it supported by Serverless framework v2? I need to double-check that, but I think...

@neerajg5 Usually, dynamodb/database operations are mocked in test environments (jest, mocha). As you said, the simulator is only a simulator for local testing. It is not meant for automated testing....

Hi @shawnmclean I believe what you are looking for is schema federation. unfortunately, this is not supported by AppSync. This plugin do support schema stitching though and you should be...

@HannaSanford Sorry for late attention. The validation of the schema relies on the [graphql](https://www.npmjs.com/package/graphql) package. I realize that we are far behind in term of version. I am not sure...

@HannaSanford I am not able to reproduce this issue. Is this still happening? If I understand correctly, your schema file has the annotations after the `implements`, but when deploying it...

That's right, it's supported by a third party. I forgot to mention that. However, the plugin uses "native" [validation](https://github.com/functionalone/serverless-iam-roles-per-function/blob/master/src/lib/index.ts#L54) and [type](https://github.com/serverless/serverless/blob/master/lib/plugins/aws/provider.js#L484) So, this problem also happens [here](https://github.com/serverless/serverless/blob/master/lib/plugins/aws/provider.js#L971) in the framework...

@Xocix Are you still experiencing this issue?

@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...

Thanks, @sweepy84 This is definitely something I'd like to see in the plugin I'll try to get something done in the following days.

@ankon Yes!. That sounds good. Usually, the schema is in the same or in a subdirectory of the repository, but I don't see any issue with using Absolute paths. Feel...