Use direct R2 vcpkg cache - #6
Merged
Merged
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
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.
Switch vgi-cpp CI from the stale
VCPKG_CACHING_AWS_*configuration to Haybarn's direct Cloudflare R2 pattern.query-farm-duckdb-vcpkgthrough the R2 S3-compatible endpointR2_*credentials andregion=autos3..amazonaws.comrequestsHAYBARN_VCPKG_TOKENis deliberately not used because it authenticates the Worker path, whose request-size limit is unsuitable for large vcpkg archives.