34282926a1
## What Generates version 2.0 of the Airbyte platform documentation using Docusaurus's built-in versioning system. This creates a frozen snapshot of the current documentation that users can reference. Requested by ian.alton@airbyte.io via [Slack thread](https://airbytehq-team.slack.com/archives/D08FX8EC9L0/p1760490197805979?thread_ts=1760490197.805979). Link to Devin run: https://app.devin.ai/sessions/689693593bac44f4903f476aa17b872e ## How - Ran `pnpm run docusaurus docs:version:platform 2.0` in the docusaurus directory - This automatically: - Created `platform_versioned_docs/version-2.0/` containing a snapshot of all current platform docs - Created `platform_versioned_sidebars/version-2.0-sidebars.json` with the sidebar navigation structure - Updated `platform_versions.json` to add "2.0" to the version list - Ran prettier to format the JSON files - Verified the documentation builds successfully locally (build completed in ~3 minutes with only pre-existing broken anchor warnings) ## Review guide 1. **Verify timing**: Confirm this is the correct time to release version 2.0 of the documentation 2. **Version order**: Check `docusaurus/platform_versions.json` - verify "2.0" is first in the array (newest version first) 3. **Build verification**: Ensure CI/Vercel builds pass without errors 4. **Spot check**: Optionally review 2-3 files in `docusaurus/platform_versioned_docs/version-2.0/` to ensure content looks reasonable Note: This is a standard Docusaurus versioning operation that creates a frozen snapshot of the current "next" documentation. The generated files are extensive (500+ files) but follow Docusaurus conventions. ## User Impact Users will see version 2.0 available in the version dropdown on docs.airbyte.com. This provides a stable reference point for platform documentation at this point in time. Existing versions (1.6, 1.7, 1.8) remain unchanged. ## Can this PR be safely reverted and rolled back? - [x] YES 💚 This is an additive change that doesn't modify existing versioned docs. Reverting would simply remove version 2.0 from the version list and delete the associated documentation files. Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io>
1.8 KiB
products
| products |
|---|
| cloud |
dbt Cloud integration
By using the dbt Cloud integration, you can create and run dbt transformations immediately following syncs in Airbyte Cloud. This allows you to transform raw data into a format that is suitable for analysis and reporting, including cleaning and enriching the data.
:::note
Transforming data may cause an increase in your destination's compute cost. This cost will vary depending on the amount of data that is transformed and is not related to Airbyte credit usage.
:::
Prerequisites
- To use the dbt Cloud integration, you must use a paid version of dbt Cloud.
- The service token must have Member, Job Admin, or Account Admin permissions.
Step 1: Generate a service token
Generate a service token to enable authentication with dbt Cloud.
Step 2: Set up the dbt Cloud integration for the workspace
-
Click Workspace settings > Integrations. Enter your access URL (for example,
https://cloud.getdbt.com/). Custom access URLs are also supported. -
Enter the service token and click Save changes.
Step 3: Add a dbt transformation to an individual connection
-
Click Connections and select the connection you want to add a dbt transformation to. Go to the Transformation tab and click + Add transformation.
-
Select the dbt job from the dropdown and click Save changes. The dbt job will run after the subsequent syncs until you remove it. You can repeat these steps to add additional transformations for a connection.
-
To remove a transformation, click X on the transformation and click Save changes.