[CT-3568] print / no_print in profiles.yml has no effect

[dbeatty10]

Here's the relevant documentation about the print global config:

• https://docs.getdbt.com/reference/dbt-jinja-functions/print
• https://docs.getdbt.com/reference/global-configs/print-output

I tried specifying print: False within profiles.yml as described in the docs, but it didn't have any effect.

So maybe it was fully deprecated sometime between dbt v1.5 and v1.7 but we didn't yet update the docs? Or maybe it was accidentally stopped working during the click migration (in dbt-labs/dbt-core#7086)?

Originally posted by @dbeatty10 in #4740 (comment)

To do

Try out the following within each of v1.5, v1.6, and v1.7. Figure out if it was fully deprecated or not and update the docs accordingly.

1. Create this simple model file:

models/my_model.sql

{{ print("") }}
{{ print("*** Parsing, compiling, or running: " ~ this) }}
{{ print("") }}

select 1 as id

2. Add the following config to profiles.yml:

config:
  print: False

3. See if *** Parsing ... shows up in the logs or not:

dbt parse

[runleonarun]

Hey @dbeatty10, I came across a possibly related Slack convo. It maybe needs to be wrapped in a macro until it's fixed in Core?

[dbeatty10]

Hey @dbeatty10, I came across a possibly related Slack convo. It maybe needs to be wrapped in a macro until it's fixed in Core?

Oooh, good call about that Slack convo 🧠

Digging into that convo deeper, it seems it is mainly related to other issues like these:

• [CT-3175] Convert print call sites to logging events dbt-core#8756
• [CT-3432] [spike] investigation - event system should completely control stdout dbt-core#9174

Looking at this more closely, I think this might be a bug in dbt-core, so I'm going to transfer this issue to that repo.

[dbeatty10]

See also: dbt-labs/dbt-core#7036 (which also mentions print and would presumably resolve this issue).

[dbeatty10]

After further research, I think we just need an update to the docs.

Opened #4775 to address this.