Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enable/disable option not working for shared API GW

See original GitHub issue

When using shared API GW, the global configuration apiGatewayCaching.enable and endpoint configuration caching.enable doesn’t work as expected. As long as the cache is enabled for shared API GW, it will be enabled for all individual endpoints in it.

Wondering is those two options designed only for dedicated API GWs? Thanks

Issue Analytics

State:
Created 2 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

DianaIonitacommented, Mar 1, 2022

it also means unnecessary overhead in our case since our purpose is just to turn the cache off

True, though it’s uncertain that it would impact the endpoint. It’s a good point though, I’ll try asking AWS support what their thoughts are on the matter. Thanks for raising this!

1reaction

GaaraZhucommented, Feb 27, 2022

Thanks @DianaIonita for such a detailed reply. This is very helpful. Previously we only applied the plugin in the endpoint config not the shared API GW. I’ll have another try and let you know whether it works or not. Thanks