aboutsummaryrefslogtreecommitdiffstats
path: root/python/servo/mutation
diff options
context:
space:
mode:
authorMukilan Thiyagarajan <mukilanthiagarajan@gmail.com>2023-01-26 11:43:39 +0530
committerMukilan Thiyagarajan <mukilanthiagarajan@gmail.com>2023-01-26 18:15:37 +0530
commite4764e76616d4da6ebb3875cedf790a0f08337bd (patch)
treee8fa55f3bd5ee58508d7b06b169a87e41f9ede14 /python/servo/mutation
parent4f355f5877878bb2f4aed2b471e82722cd43f8e1 (diff)
downloadservo-e4764e76616d4da6ebb3875cedf790a0f08337bd.tar.gz
servo-e4764e76616d4da6ebb3875cedf790a0f08337bd.zip
Invalidate latest nightly files in CloudFront.
After a new nightly build is uploaded to S3, bust the cache in CloudFront Edge servers with the CreateInvalidation AWS API. For each platform we use the `/nightly/<platform>/servo-latest.<ext>*` pattern to invalidate both package and sha256 files. As part of this change, a new policy has been attached to the "download.servo.org-uploads-from-travis" IAM user to allow the "cloudfront:CreateInvalidation" action. Since CloudFront [invalidates every version][1] of the cached file, regardless of the headers used for that version, this change should invalidate the different caches for 'Accept-Encoding' header. [1]: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#invalidation-specifying-objects Closes #29034 Signed-off-by: Mukilan Thiyagarajan <mukilanthiagarajan@gmail.com>
Diffstat (limited to 'python/servo/mutation')
0 files changed, 0 insertions, 0 deletions