Invalidate CloudFront Cache when republishing engine files with same engine hash #10328
Labels
kind/tech
A technical change.
team/client
Issue for team Client.
tech/engines
Issue for tech Engines.
topic: binary distribution
topic: ci/cd
topic: engine download
#10312 was caused by a caching layer in front of our engine file distribution, that did not get updated when we reuploaded the same engine version (
78a5df6def6943431f4c022e1428dbc3e833cf8e
) via a new build of the same commit hash (https://buildkite.com/prisma/release-prisma-engines/builds/1768 vs https://buildkite.com/prisma/release-prisma-engines/builds/1767).The solution was to manually invalidate the CloudFront cache that sits in front of the S3 bucket where we store these files.
We should integrate invalidating that cache when we re-upload already existing Engine files so this is automated.
The text was updated successfully, but these errors were encountered: