jobs/sync_to_sparse_index: Add Fastly CDN support #12451
Merged
+28
−3
Conversation
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
Turbo87
added
the
C-enhancement ✨
2 tasks
LawnGnome
approved these changes
Dec 5, 2025
Turbo87
force-pushed
the
fastly-sparse-index
branch
from
c01554f to
ba66537
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds a
SPARSE_INDEX_FASTLY_ENABLEDenvironment variable, which tells theSyncToSparseIndexbackground job to also send invalidation requests to Fastly (in addition to Cloudfront).We are in the process of shifting more traffic towards Fastly for cost reasons, and this PR is part of that effort, since the sparse index had so far been provided exclusively on Cloudfront.