We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*
Not sure if it has been the cause of certain bugs / issues we may be seeing in regards to inconsistent data on the frontend side of the project, but I wonder if the issue is how we are submitting our cache invalidation?
const params = { DistributionId: CONFIG.distributionId, InvalidationBatch: { CallerReference: new Date().getTime(), Paths: { Quantity: 1, Items: [ `/api/v2/${entity}s` ] } } };
I've always used a wildcard in these types of scenarios, so I'm thinking the code should be updated accordingly
const params = { DistributionId: CONFIG.distributionId, InvalidationBatch: { CallerReference: new Date().getTime(), Paths: { Quantity: 1, Items: [ `/api/v2/${entity}s/*` ] } } };
The text was updated successfully, but these errors were encountered:
thescientist13
Successfully merging a pull request may close this issue.
Not sure if it has been the cause of certain bugs / issues we may be seeing in regards to inconsistent data on the frontend side of the project, but I wonder if the issue is how we are submitting our cache invalidation?
I've always used a wildcard in these types of scenarios, so I'm thinking the code should be updated accordingly
The text was updated successfully, but these errors were encountered: