ci: purge the Bunny CDN zone on every deploy - #58
Merged
Merged
Conversation
One POST to the pull-zone purge endpoint, reading BUNNYCDN_ZONE_ID (or BUNNYCDN_DEV_ZONE_ID where that is the secret the repo has). Some pipelines read a secret the repo does not have, so Bunny answered "The request is invalid." and nothing was purged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every deploy purges the Bunny pull zone with one POST to
https://api.bunny.net/pullzone/$ZONE_ID/purgeCache, the same step across the fleet.Fixes pathscale.com, web3.trading and js.software, whose purge read
BUNNYCDN_DEV_ZONE_ID(pathscale.com and web3.trading do not have it) and got "The request is invalid.", so the edge kept serving the oldindex.html. Tested locally against the pathscale.com zone: HTTP 204, edge refetched.