docs(destinations): add 11 warehouse/storage/queue destination pages (ENG-4130) - #695
Merged
Conversation
…(ENG-4130) Add pages for ClickHouse, Snowflake, BigQuery, Redshift, Azure Blob Storage, Google Cloud Storage, Amazon SQS, Amazon SNS, Amazon EventBridge, Google Cloud Pub/Sub, and RabbitMQ, modeled after the existing Kinesis/S3 destination pages. Register them in generate-docs.ts (regenerated docs.json) and update the destinations overview. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…tions (ENG-4130) Warehouse pages now document the exact table the sink expects (BigQuery id/payload; Snowflake id/created_at/payload; Redshift created_at/payload; ClickHouse one column per top-level field) plus the optional batchSize/maxWaitSecs. Overview adds a "Considerations" section: pre-created warehouse tables, batching, the 10-per-project sink limit, and the GCS/Azure object-naming caveat. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Merge table-setup + message-format into a "Data format" section placed before "Refer to the destination", linking to webhook.yaml for the payload schema. - Warehouses show the table they need: ClickHouse maps top-level keys to columns (example with ...); BigQuery/Snowflake/Redshift load the payload into a single column (id/created_at/payload as applicable). - Add an Example column to every "Create a destination" table. - Remove em dashes, remove "we store credentials securely" notes, and remove all vendor (Svix) references. - Alphabetize the Destinations sidebar; drop the overview "Considerations" section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-4130) - Remove "read fields with X's JSON functions" guidance from BigQuery, Snowflake, and Redshift; the pages describe only the table shape Ampersand writes to. - Remove the "Ampersand encrypts and stores your credentials securely" notes from the S3 and Kinesis pages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
laurenzlong
approved these changes
Aug 18, 2026
Nest the Destinations sidebar into Queues (EventBridge, Kinesis, Pub/Sub, RabbitMQ, SNS, SQS), Databases and warehouses (BigQuery, ClickHouse, Redshift, Snowflake), and Blob storage (Azure Blob, GCS, S3). Overview and Webhooks stay top-level. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Blob-storage sinks write objects with an uncontrolled `object-generated-by-svix` prefix, so hold them back until we own the naming. Remove the azure-blob and gcs pages and their sidebar entries; S3 stays under "Blob storage". See Linear ENG-4200. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…200) Remove the Object storage section (Azure Blob + GCS) and the prose mentions from the destinations overview so the broken-links check passes. See Linear ENG-4200. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… note - Remove the duplicate destinations/kinesis from the Queues group (it's a top-level destination, matching the overview); regenerate docs.json. - Redshift: mark Workgroup name / Cluster identifier as No* and clarify the note that exactly one is required (addresses Graphite review comment). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…egories Top-level overview/webhooks/slack, followed by the categories alphabetically (Blob storage, Databases and warehouses, Queues). Kinesis moves into Queues. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Keep only Webhook and Slack at the top level; move Amazon S3 under a Blob storage heading and Amazon Kinesis into Message queues and event buses, matching the sidebar structure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
RajatPawar
enabled auto-merge (squash)
August 18, 2026 23:27
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
2 participants
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.
Documents the 11 new Svix stream-sink destination types shipped in server#7057 / openapi#394.
New pages (
src/destinations/)Data warehouses:
clickhouse,snowflake,bigquery,redshiftObject storage:
azure-blob,gcsMessage queues / event buses:
sqs,sns,eventbridge,pubsub,rabbitmqEach page follows the existing Kinesis / S3 destination page structure — intro, prerequisites, a config-field table matching the dashboard fields, an
amp.yamlreference example, and a message-format section linking to the canonical read/subscribe payload schema.Other changes
src/generate-docs.tsand regeneratedsrc/docs.json.destinations/overview— moved the newly-supported types out of the roadmap into a grouped "Supported destinations" list.