Advanced dbt Features
This page describes advanced dbt features supported by Etleap.
Packages
Etleap will install any dbt packages specified in your dbt project.
Target Variables
Etleap sets the following target variables for each type of run. Production values apply to scheduled runs; development values apply to draft and CI builds.
| Variable | Production value | Development value |
|---|---|---|
target.database | The database configured in the dbt Schedule’s connection | The database configured in the Development Warehouse connection |
target.name | "prod" | "ci" |
target.threads | 4 | 4 |
These values are available in dbt Jinja templates as {{target.database}}, {{ target.name }}, and {{ target.threads }}.
These values can be used in macros to branch behaviour by environment .
dbt Environment Variables
Org admins can configure custom environment variables that are injected into dbt builds. Each variable has separate values for Production and CI Development:
- Production values are used by dbt Schedules.
- CI Development values are used by PR builds and drafts in the dbt editor.
To manage environment variables:
- Go to Admin Console → dbt Settings.
- Under Environment Variables:
- To add a variable, enter a name and values for Production and CI Development in the new entry row.
- To modify a variable, edit the name or values in an existing row.
- To remove a variable, click the delete icon next to the row.
- Click Save changes.
When configuring environment variables:
- Names must start with
DBT_followed by at least one capital letter, number, or underscore.. - The name
DBT_JOB_CONF_PATHis reserved and cannot be used.