Implelement Tuist Caching Protocol #792
Open
Conversation
This file contains 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
edigaryev
force-pushed
the
tuistcache
branch
from
06b32ed
to
96c08eb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've deliberately chosen
CIRRUS_TUIST_CACHE_URLoverCIRRUS_TUIST_CACHE_HOSTbecause (1) this will free us from path collisions in the HTTP cache in the future and (2) because this is what OpenAPI normally expects when instantiating a client.The only issue right now is that Tuist caching protocol does not give a hint as to what
Content-Lengthwill be used when performingUploadPartrequest, yet this header is required by Cloudflare R2, see cirruslabs/chacha#4.