dbt Core

Catalog integrates well with dbt, it only requires the manifest.json generated by dbt to be sent to Catalog whenever it's updated or on a daily basis.

For sync back to dbt, please refer to: Sync back to dbt

Where is the manifest?

It's within the target directory

Make sure to retrieve the manifest from your production environnement. The one that actually points to your production tables. Otherwise the matching done by database.schema.table.column won't work

How and how often to send the manifest

1. During your trial, you can simply upload it via the Integration page

2. Afterwards, we'll provide you with a Source ID and a Catalog Token to use our Catalog Uploader

1. One Shot load

During your Catalog trial we offer a one-shot sync of your descriptions. Simply upload it in the App when creating your dbt Managed by Yourself integration

2. Scheduled sync

The Catalog team will provide you with

1. A Catalog Source id (to send your manifest to)

2. A Catalog Token

To be used with our uploader:

⬆️Uploader

We can also share a standalone python script to upload your manifest without the need of our pypi package. Please reach out to your Catalog point of contact for further information.

Scheduling the sync

• You can schedule it using your classic Airflow workflow.

• If your dbt is on Github see the page link below

• Or you can do it your any way you deem better 😊

Github actions for dbt sync

Going further

Once your dbt integration is set up, seize the full potential of dbt and Gitlab:

• dbt Sync back

• dbt Owners