Seed configurations
Available configurations
Seed-specific configurations
General configurations
Configuring seeds
Seeds can only be configured from the dbt_project.yml
file, under the seeds:
key. To apply a configuration to a seed, or directory of seeds, define the resource path as nested dictionary keys.
Seed configurations, like model configurations, are applied hierarchically — configurations applied to a marketing
subdirectory will take precedence over configurations applied to the entire jaffle_shop
project.
Examples
schema
configuration to all seeds
Apply the To apply a configuration to all seeds, including those in any installed packages, nest the configuration directly under the seeds
key:
seeds:+schema: seed_data
schema
configuration to all seeds in your project
Apply the To apply a configuration to all seeds in your project only (i.e. excluding any seeds in installed packages), provide your project name as part of the resource path.
For a project named jaffle_shop
:
seeds:jaffle_shop:+schema: seed_data
Similarly, you can use the name of an installed package to configure seeds in that package.
schema
configuration to one seed only
Apply the To apply a configuration to one seed only, provide the full resource path (including the project name, and subdirectories).
For a project named jaffle_shop
, with a seed file at data/marketing/utm_parameters.csv
, this would look like:
seeds:jaffle_shop:marketing:utm_parameters:+schema: seed_data
Example seed configuration
The following is a valid seed configuration for a project with:
name: jaffle_shop
- A seed file at
data/country_codes.csv
, and - A seed file at
data/marketing/utm_parameters.csv
name: jaffle_shop...seeds:jaffle_shop:+enabled: true+schema: seed_data# This configures data/country_codes.csvcountry_codes:# Override column types+column_types:country_code: varchar(2)country_name: varchar(32)marketing:+schema: marketing # this will take precedence