-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: add include_bucket_in_prefix param to bulk exports documentation #1753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Mintlify preview ID generated: preview-ENT210-1764966091-fd259a2 |
35d872e to
28b68f0
Compare
|
Mintlify preview ID generated: preview-ENT210-1764983233-eef25b8 |
|
Mintlify preview ID generated: preview-ENT210-1764983856-47d534e |
|
Mintlify preview ID generated: preview-ENT210-1764985022-9099905 |
| - **Endpoint URL**: The endpoint URL for the S3 bucket - this is needed for S3 API compatible buckets. | ||
| - **Access Key**: The access key for the S3 bucket. | ||
| - **Secret Key**: The secret key for the S3 bucket. | ||
| - **Include Bucket in Prefix** (optional): Whether to include the bucket name as part of the S3 path prefix. Defaults to `false` for new destinations. Set to `true` for legacy compatibility or when using S3-compatible storage systems that require the bucket name in the path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this always required for AWS S3, but not GCS?
Overview
Add documentation for recently added
include_bucket_in_prefixoptional param when creating destinations for bulk exportsType of change
Type: Update existing documentation
Related issues/PRs
Checklist
docs devsrc/docs.jsonif needed(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow
Additional notes