Benoît Bouré

Thanks for the insights. I like the idea. I see several things we could try to do as you suggested. - try to infer the caching keys from `caching` config...

Are you talking about the simulator or real deployed AppSync? Looks like you are talking about the [simulator](https://github.com/bboure/serverless-appsync-simulator), so this is the wrong repo to ask related questions. The simulator...

Hi @zhaoyi0113 are you doing this intentionally in order to split concerns or is it due to the CloudFormation restriction on stack size? For the Cfn restrictions, there is [this...

@zhaoyi0113 I think I know what you mean now. The only thing you can really separate are the data sources (Lambda functions, Dynamodb tables, etc) Then, you can reference them...

All right, I understand. This is not something we support right now. However I guess we could consider this feature. This could probably help too with other issues like #194

@zhaoyi0113 Would you feel like opening a PR yourself to solve this particular issue? Since you have a real use-case, and understand the problem well, it might help finding the...

@EwanValentine I'd like to make sure I understood your issue. So, you have several microservices all exposed through the same graphql. Are all microservices in different stacks/serverless.yml? If so, what...

@EwanValentine I assume that you are using lambdas for your microservices? What about this: Have your microservices only deploy a lambda with your code. No Appsync involved here. In your...

@kkesley @EwanValentine I had a second look at this, I think that what you need is to be able to manually override [this parameter](https://github.com/sid88in/serverless-appsync-plugin/blob/master/index.js#L600), and specify an AppSync arn from...

@kkesley I also see it as an AppSync limitation rather than the plugin. If you are going to manage the schema in the parent stack, then what I can suggest...