Skip to content

Releases: DianaIonita/serverless-api-gateway-caching

1.2.2

15 Jan 11:02
Compare
Choose a tag to compare

Changes Summary

#26 Fixed issue where caching could not be applied to an endpoint with a path parameter containing underscores. Also fixed issue where, if one endpoint could not be found in the compiled CloudFormation template, no other subsequent endpoint would have their caching parameter settings updated.

1.2.1

17 Dec 11:15
Compare
Choose a tag to compare

Changes Summary

#21 Supporting the + character in http event paths

1.2.0

13 Dec 17:40
Compare
Choose a tag to compare

Changes Summary

#18 Added support for multiple HTTP events per function and support for custom function names (Thanks to @LuciCondescu)

1.1.6

27 Nov 21:56
Compare
Choose a tag to compare

Changes Summary

#20 Added support for cases when the Rest API was created in another stack and is referenced in the yaml

1.1.5

25 Nov 14:58
Compare
Choose a tag to compare

Changes Summary

#17 Fixed issue where path parameters weren't being configured on functions with names substrings of other functions. For example, if there was a function named catpaw and a function named paw, path parameters were not configured for the paw function.

1.1.4

10 Oct 19:04
Compare
Choose a tag to compare

Changes Summary

#13 No longer setting that path parameters are required on request validation. If that has been set by something else - for instance, via the Resources section in serverless.yml or via another plugin - the value is kept.

1.1.3

24 Sep 10:48
Compare
Choose a tag to compare

Changes Summary

  • Fixed npm package version issue

1.1.2

24 Sep 10:46
Compare
Choose a tag to compare

Changes Summary

#10 Fixed issue where plugin would cause deployment to fail when no Rest API is defined in serverless configuration

1.1.1

20 Sep 20:39
Compare
Choose a tag to compare

Changes Summary

1.1.0

19 Sep 15:45
Compare
Choose a tag to compare

Changes Summary

  • Added support for configuring per-key cache invalidation authorization
  • Removed the option to specify whether cache key parameters are required or not, since that appears to have no effect on API GW caching and is likely used with request validators.