Skip to content

Commit

Permalink
Remove duplicate printer_width entry in profiles.yml.md
Browse files Browse the repository at this point in the history
  • Loading branch information
dangoldin committed Feb 1, 2024
1 parent 8cab976 commit c9fce76
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions website/docs/docs/core/connect-data-platform/profiles.yml.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,14 @@ title: "About profiles.yml"
id: profiles.yml
---

If you're using [dbt Core](/docs/core/installation-overview), you'll need a `profiles.yml` file that contains the connection details for your data platform. When you run dbt Core from the command line, 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.
If you're using [dbt Core](/docs/core/installation-overview), you'll need a `profiles.yml` file that contains the connection details for your data platform. When you run dbt Core from the command line, 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](/docs/core/connect-data-platform/connection-profiles).

:::tip No `profiles.yml` file needed for dbt Cloud
If you're using dbt Cloud, you can [connect to your data platform](/docs/cloud/connect-data-platform/about-connections) directly in the dbt Cloud interface and don't need a `profiles.yml` file.
:::


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.

<File name='profiles.yml'>
Expand All @@ -32,7 +31,6 @@ This section identifies the parts of your `profiles.yml` that aren't specific to
[use_experimental_parser](/reference/global-configs/parsing): <true | false>
[static_parser](/reference/global-configs/parsing): <true | false>
[cache_selected_only](/reference/global-configs/cache): <true | false>
[printer_width](/reference/global-configs/print-output#printer-width): <integer>

<profile-name>:
target: <target-name> # this is the default target
Expand Down

0 comments on commit c9fce76

Please sign in to comment.