Repository navigation
docs: say the S3-compatible part is the API, not the storage - #47
Merged
Merged
Conversation
Data on Source is stored with several providers, including Azure Blob Storage, which does not speak S3. What is S3-compatible is the data proxy's API, which serves every product the same way regardless of where it is stored. what-is-source.md now says that. create-an-account.md listed AWS CLI access as needing an account, but the Access Data page shows public data working with --no-sign-request. The bullet now says the account is for restricted data. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Two wording fixes about S3 compatibility.
what-is-source.md: "Data on Source is stored in S3-compatible object storage" isn't true for every product. Some products are stored in Azure Blob Storage, which doesn't speak S3 (the same page thanks Azure for hosting). What is S3-compatible is the data proxy's API: the proxy uses multistore, which reads Azure through
object_store's native Azure backend and serves the result to clients over the S3 API. The sentence now says that data is served through an S3-compatible API, whichever cloud stores it.create-an-account.md: the list of things that need an account included "Accessing data programmatically via AWS CLI", but Access Data shows public data working with
--no-sign-requestand no account. The bullet now says restricted data.The other mentions of S3 compatibility (data-proxy.md, core-concepts.md, upload/index.md, create-an-account.md's credentials bullet) describe the proxy's API, its clients or its credentials, and still hold.