Repository navigation
Conversation
Adds a Data Connections section to the Core Concepts page, defining what a data connection is, its key configuration fields, and linking to the Bring Your Own Bucket guide for setup instructions. Closes #41 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
A data connection can point at S3 (or an S3-compatible store such as R2), Azure Blob or Google Cloud Storage, not only S3. Source's own storage is also configured as data connections, so the section no longer presents them as BYOB-only. The authentication bullet now describes what the data proxy serves today: no authentication, or federated access via an assumed IAM role. The read-only rule is tied to having no authentication, not to public visibility, and the section says creating connections must be enabled for an account. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The data proxy prepends a connection's base prefix to every object key whatever the provider, so for Azure it is a folder inside the container. The Base Prefix bullet now says bucket or container, matching the Location bullet. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The section's closing line already points to the BYOB page for setup, matching the single see-also link that ends the Data Products section, so the first mention is now plain text. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
@alukach for accuracy review |
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.
Summary
Adds a Data Connections section to the Core Concepts page (
docs/about-source/core-concepts.md), between "Objects" and "Data Viewers", and links to the Bring Your Own Bucket page for setup.A data connection describes a storage location and how Source accesses it. It can be an Amazon S3 bucket (or an S3-compatible store such as Cloudflare R2), an Azure Blob container, or a Google Cloud Storage bucket (
DataProviderin source.coop'ssrc/types/data-connection.ts). Source's own storage is configured as data connections too, ones with no owner, and BYOB lets an account add connections to storage it controls.The section lists the fields in the page's bullet style:
backend_auth.rsin data.source.coop). The schema also defines access-key and SAS-token types, but the proxy refuses them, and the GCP and Azure workload-identity types are scaffolded but not implemented, so the docs leave them out.DataConnectionSchema's refinement).It also notes that creating connections must be enabled for an account (the
CREATE_DATA_CONNECTIONSaccount flag), which matches the BYOB page's beta note.Closes #41
Test plan
/bring-your-own-bucketresolves (docs/using-source/bring-your-own-bucket.mdhas that slug)🤖 Generated with Claude Code