Implement Caching

[bboure]

Resolves #276

[bboure]

@michaelrhoden Want to help testing this?

[rakeshmenon]

@bboure - Is this tested or do you need any help?

I've created a PR to your branch (feature/caching) to fix the failing snapshots.

[bboure]

@rakeshmenon I haven't tested this (yet).
Any help is appreciated :)

[rakeshmenon]

@bboure I was not able to get it to work.

I tried using it by changing the package version to:
sid88in/serverless-appsync-plugin#feature/caching

I added the caching configuration in serverless.yml as follows -

Under appSync:

  caching:
      ttl: 60
      behavior: PER_RESOLVER_CACHING
      type: 'T2_SMALL'

Under each mapping template:

  caching:
      ttl: 30

It was an update stack operation - as the AppSync endpoint already exists. The update stack operation went through - but did not enable the caching options in the resolvers or change the global caching config.

Let me know what you need from my end to debug this issue.

[bboure]

THank you @rakeshmenon for testing this.
Can you confirm that the plugin got updated correctly in your node_modules folder?

instead of changing your package.json, you can also try to use npm link or yarn link

[rakeshmenon]

Yes - the plugin was updated in the node_modules directory.

[bboure]

Fixed some issues and this is almost working as expected.
I came across an issue when disabling cache on a resolver. It seems related to CloudFormation.
I opened an issue here

[rakeshmenon]

w00t! I'll test this out today. Hopefully the Cloudformation issue gets addressed soon :)

[rakeshmenon]

Have tested this PR - I faced the same issue. Caching at the resolver level is not clearing when I removed caching config.

Everything else works fine!

[bboure]

Cfn bug has been confirmed by AWS. After testing this on us-east-2 where the bug has been fixed. All seems to be working s expected.
Will merge this soon

[rakeshmenon]

Hi @bboure - when will the new version of the plugin be published with this change included?

[bboure]

@rakeshmenon the plan is to release soon.
I just want to make sure that there are no breaking changes

[bboure]

@rakeshmenon This is now part of the v1.2.0 release. Enjoy!