DBT Core
This article outlines the integration with the DBT Core connector, enabling streamlined metadata management through features such as crawling and lineage building (both automatic and manual).
The connector uses secure authentication through the Credential Manager to ensure controlled access. It connects to the data source using either an Amazon S3 bucket or a Network File System (NFS) path, allowing users to crawl manifest files and build data lineage.
NFS (Network File System) is a distributed file system protocol that allows users to access files stored on remote servers as if they were stored locally. In DBT Core integrations, NFS is typically used when manifest files are generated and stored within on-premises environments or shared file systems accessible through mounted directories.
Amazon S3 (Simple Storage Service) is an object storage service used to store and retrieve files through cloud-based buckets. In DBT Core integrations, S3 is commonly used to store DBT artifacts such as
manifest.jsonfiles generated during DBT runs.
Overview
Connector Details
Connector Category
ETL Tool
OvalEdge Release Supported
Release6.1 to Release7.2.3
Connectivity
[How OvalEdge connects to DBT Core]
S3 Bucket/NFS
Verified DBT Core Version
1.7.6
The DBT Core connector has been validated with the mentioned "Verified DBT Core Version" and is expected to be compatible with other supported DBT Core versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
Connector Features
Crawling
✅
Delta Crawling
❌
Profiling
❌
Data Preview
❌
Auto Lineage
✅
Manual Lineage
✅
Secure Authentication via Credential Manager
✅
Data Quality
❌
DAM (Data Access Management)
❌
Bridge
✅
Metadata Mapping
The following objects are crawled from DBT Core and mapped to the corresponding UI assets.
Manifest.json
Manifest.json File
Code Name
Codes
DBT_RUN
SQL's inside Manifest file
SQL's inside Manifest file
Code Name
Codes
DBT_RUN_SQL
Set up a Connection
Prerequisites
The following are the prerequisites to establish a connection:
Service Account User Permissions
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
👨💻Who can provide these permissions? These permissions are typically granted by the administrator, as users may not have the required access to assign them independently.
Crawling
Datasets
Read only
Connection Configuration Steps
Users are required to have the Connector Creator role in order to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for DBT Core, and complete the required parameters.
Fields marked with an asterisk (*) are mandatory for establishing a connection.
Connector Type
By default, "DBT Core" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. The corresponding parameters will be displayed based on the selected option.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp
Azure Key Vault
License Add Ons
Select the checkbox for the Auto Lineage Add-On to build data lineage automatically.
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
Connector Name*
Enter a unique name for the DBT Core connection
(Example: "DBTCore").
Connector Description
Enter the description related to the connector.
DBT core repository type*
Select the type of DBT Core repository from the dropdown menu.
NFS
S3
Path*
Enter the path to the location where the DBT Core files are stored.
Authentication*
Select the type of Authentication from the dropdown menu.
IAM User Authentication
Role-Based Authentication
S3 Bucket name*
Enter the name of the S3 bucket where the DBT Core files are stored.
S3 zip pathname name
Enter the path name where the zip file was extracted from the manifest file in the project folder.
Access key*
Enter the AWS Access Key ID used to authenticate the IAM user.
Note: This field is available only when the Authentication is set to “IAM User Authentication”.
Secret key*
Enter the AWS Secret Access Key associated with the Access Key ID.
Note: This field is available only when the Authentication is set to “IAM User Authentication”.
Cross-Account Role ARN
Enter the ARN (Amazon Resource Name) of the role used for cross-account access.
Note: This field is available only when the Authentication is set to “Role-Based Authentication”.
Filter by tags
Enter one or more tags to narrow down and display only the items associated with those tags.
Region
Enter the region where the DBT Core files or resources are located.
Default Governance Roles
Default Governance Roles*
Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.
Admin Roles
Admin Roles*
Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in the security settings are available for selection.
No of Archive Objects
No Of Archive Objects*
This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.
Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*
If applicable, select the bridge from the drop-down list.
The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl
To perform crawl and profile operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more schemas for crawling.
Navigate to the Connectors page and click Crawl/Profile.
Select the schemas to crawl.
The Crawl option is selected by default.
Click Run to collect metadata from the connected source and load it into the Data Catalog.
After a successful crawl, the information appears in the Data Catalog > Databases/<>Codes tab.
The Schedule checkbox allows automated crawling at defined intervals, from a minute to a year.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time interval for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
The system will automatically execute the crawl operation at the scheduled time.
Other Operations
The Connectors page provides a centralized view of all configured connectors, along with their health status.
Managing connectors includes:
Connector Health: Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
Viewing: Click the Eye icon next to the connector name to view connector details, including databases, tables, columns, and codes.
Nine Dots Menu Options:
To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.
Edit Connector: Update and revalidate the data source.
Validate Connector: Check the connection's integrity.
Settings: Modify connector settings.
Crawler: Configure data extraction.
Access Instructions: Add notes on how data can be accessed.
Business Glossary Settings: Manage term associations at the connector level.
Others: Configure notification recipients for metadata changes.
Build Lineage: Automatically build data lineage using source code parsing.
Delete Connector: Remove a connector with confirmation.
Additional Information
Manifest File Path Requirements
For both NFS and S3 repository types, ensure the DBT Core manifest file is stored under the target folder using the following path structure:
Create a folder named
targetin the configured NFS path or S3 bucket path.Rename the JSON file as
manifest.json.Custom folder names or manifest file names are not supported.
Connectivity Troubleshooting
If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.
1
Invalid File Path
Description: The specified NFS or S3 file path is incorrect or not accessible.
Resolution:
Verify the file path is correct.
Ensure the path exists and is accessible.
Check required permissions for the path.
2
Authentication Failed
Description: The provided credentials are invalid or not authorized.
Resolution:
Validate access key and secret key.
Verify mount or connection credentials.
Ensure the credentials have required access permissions.
Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA
Last updated
Was this helpful?