-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
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
Invalidate CDN caches after uploading database dump #6656
Conversation
An implementation for cache invalidations on Fastly has been added. Specific paths can be invalided using Fastly's cached URL endpoint, but this does not support wildcard invalidations. Documentation on Fastly's invalidation API can be found here: https://developer.fastly.com/reference/api/purging/
After uploading a new version of the database dump, the cached version needs to be invalidated in CloudFront and Fastly.
When invalidating a CDN fails, we want to log a warning and continue execution. This ensures that invalidations against all CDNs are attempted.
An instance of the Fastly struct has been added to the `Environment` so that it can be shared between jobs.
If the API token for Fastly is missing in the environment, skip invalidating the cache there. This makes it possible to opt-in to the new feature.
Thanks for jumping on this so quickly! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like production might have the wrong fastly credentials? 🤔 |
As a quick status update: I was able to confirm the issue, but unable to resolve it. Messaged Fastly support, since it looks like the problem might be on their side. Will update here when the issue is resolved. |
After uploading a new version of the database dump, the cached version needs to be invalidated in CloudFront and Fastly.
Fixes #6652