Azure
Add header support for caching
Why make this change?
Closes https://github.com/Azure/data-api-builder/issues/2604
What is this change?
Inside of the SqlQueryStructure, there is a private constructor, that all of the public constructors will call. This private constructor offers a single point where all of the queries will bottleneck, and therefore we add the cache control information to the query structure at this point. Then when we are in the SqlQueryEngine, we can check for this cache control information and handle the query appropriately.
The cache control options can be found
here: https://github.com/Azure/data-api-builder/issues/2253
and here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cache-Control#request_directives
But for reference, they are no-cache, no-store, only-if-cached, which will mean we do not get from the cache, we do not store in the cache, and if there is a cache miss we return gateway timeout, respectively.
How was this tested?
Run against test suite.
Sample Request(s)
To test you need to include the relevant cache headers in the request, "no-cache", "no-store", or "only-if-cached"
![azure-pipelines[bot] avatar](https://avatars.githubusercontent.com/in/9426?v=4 "Published by a pub.dev verified publisher"){kind=small}
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.