Use cloudfront backup urls - #344
Merged
Merged
Conversation
tcampbPPU
approved these changes
Sep 21, 2026
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
2 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.
What
/v4/backup/{feed} now returns a url field holding the CloudFront signed URL. The CLI was ignoring it and was downloading the backups directly from s3. This change ensures all backup downloads use CloudFront by default.
### Why?
The api now returns CloudFront as the primary backup URL. v3 already defaulted to this but this PR enables v4 to use CloudFront by default.
(--json still exposes every regional URL)
Testing