Enabling dbt Features in Etleap

To enable dbt features that allow you to edit models, create schedules, and run preview CI builds, complete the following setup.

Etleap can connect to one dbt project repository that is hosted in GitHub.

Step 1. Grant the Etleap Github user access to your dbt project’s repo

Grant the user etleap-transforms-prod WRITE access to your repository.

Write access is required for Etleap to be able to report GitHub PR check statuses in your repository.

Step 2. Create a GitHub webhook

1. In your GitHub dbt project repository go to Settings → Webhooks → Add Webhook.
2. Configure the webhook:
   • Payload URL:
     • For Hosted US: https://github.etleap.com/webhooks
     • For Hosted EU: https://github.eu.etleap.com/webhooks
     • In private VPC deployments, you can retrieve the URL by running:

       terraform output github_webhooks_url

       Note: For more detailed instructions on configuring the webhook in your VPC, please refer to the guide here 
   • Content Type: application/json
   • SSL verification: Enable SSL Verification
   • Which events would you like to trigger this webhook?: Let me select individual events → Pull Requests
3. Save the webhook.

Step 3. Choose a target connection

Choose a Snowflake, Redshift, or Databricks Delta Lake connection that you want the preview CI builds to be executed in.

Step 4. Contact Etleap Support

Contact Etleap Support and provide the following:

• The URL of your dbt Github repository
• The connection that you chose in Step 3

Step 5. Create your dbt Project

To use dbt features, your main branch must contain a valid dbt project.
A valid dbt project is one in which dbt parse runs successfully.

At a minimum, the project must:

• Include a dbt_project.yml  file in the project’s root with required configuration defined
• Include a models folder, for either the default /models path or the first path defined in the [model-paths] field of your dbt_project.yml
• Ensure all ref() and source() Jinja calls point to existing models or sources
• Include any macros referenced in models in the project or imported packages