If you're using dbt from the command line (CLI), you'll need a
profiles.yml file that contains the connection details for your data platform. When you run dbt from the CLI, it reads your
dbt_project.yml file to find the
profile name, and then looks for a profile with the same name in your
profiles.yml file. This profile contains all the information dbt needs to connect to your data platform.
For detailed info, you can refer to the Connection profiles.
profiles.ymlfile needed for dbt Cloud
If you're using dbt Cloud, you can connect to your data platform directly in the dbt Cloud interface and don't need a
This section identifies the parts of your
profiles.yml that aren't specific to a particular data platform. For specific connection details, refer to the relevant page for your data platform.
send_anonymous_usage_stats: <true | false>
use_colors: <true | false>
partial_parse: <true | false>
write_json: <true | false>
warn_error: <true | false>
warn_error_options: <include: all | include: [<error-name>] | include: all, exclude: [<error-name>]>
log_format: <text | json | default>
debug: <true | false>
version_check: <true | false>
fail_fast: <true | false>
use_experimental_parser: <true | false>
static_parser: <true | false>
target: <target-name> # this is the default target
type: <bigquery | postgres | redshift | snowflake | other>
### database-specific connection details
<target-name>: # additional targets
<profile-name>: # additional profiles
You can set default values of global configs for all projects that you run using your local machine. See the docs on global configs for details.