Skip to content

Commit 8d6c1a8

Browse files
committed
Extensions, not integrations
1 parent b6b3f78 commit 8d6c1a8

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

src/segment-app/extensions/dbt.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
title: dbt Extension
33
---
44

5-
Segment's dbt integration lets you use [Reverse ETL](/docs/connections/reverse-etl/) with your existing dbt labs models and syncs to help centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.
5+
Segment's dbt extension lets you use [Reverse ETL](/docs/connections/reverse-etl/) with your existing dbt labs models and syncs to help centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.
66

7-
With Segment's dbt integration, you can:
7+
With Segment's dbt extension, you can:
88

99
- Securely connect Segment to the GitHub repository that stores your dbt models.
1010
- Use centralized dbt models to set up Reverse ETL.
@@ -13,19 +13,19 @@ With Segment's dbt integration, you can:
1313
This page explains how to set up a dbt Model and then use the model with Reverse ETL.
1414

1515
> info ""
16-
> Extensions, including Segment's dbt integration, is currently in public beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
16+
> Extensions, including dbt sync, is currently in public beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
1717
1818
## Before you begin
1919

20-
Keep the following in mind as you set up the dbt integration:
20+
Keep the following in mind as you set up the dbt extension:
2121

22-
- The integration supports [dbt Core v1.7](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.7){:target="_blank"}.
22+
- The extension supports [dbt Core v1.7](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.7){:target="_blank"}.
2323
- You can use Snowflake, Databricks, RedShift, Postgres, and BigQuery as Reverse ETL sources.
2424
- dbt models aren't synchronized from the dbt cloud. The model sync connects to a Git repository that loads models into Segment for use with Reverse ETL.
2525

2626
## Set up Git dbt Models and dbt Cloud
2727

28-
To set up the dbt integration, you'll need:
28+
To set up the dbt extension, you'll need:
2929

3030
- an existing dbt account with a Git repository
3131
- (for job syncs:) dbt cloud with jobs already created

src/segment-app/extensions/git.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: Git Sync Extension
55
Segment's Git extension lets you manage versioning by syncing changes you make in Sources and Destinations from your Segment Workspace to a Git repository.
66

77
> info ""
8-
> Extensions, including Segment's Git sync integration, is currently in public beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
8+
> Extensions, including Git sync, is currently in public beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
99
1010
## Set up Git sync
1111

@@ -17,6 +17,6 @@ Follow these steps to set up Git sync:
1717

1818
## Working with Git syncs
1919

20-
After you set up the Git sync integration for the first time, Segment performs an initial sync that sends source and destination information in your Segment Workspace to the Git repository you connected.
20+
After you set up the Git sync extension for the first time, Segment performs an initial sync that sends source and destination information in your Segment Workspace to the Git repository you connected.
2121

2222
You can run syncs at any time by clicking **Full resync** on the Git sync page. To disable Git sync from the Git sync page, switch the **Enabled** toggle to off.

0 commit comments

Comments
 (0)