Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

When attempting to use `DbtCoreOperation` we are receiving the following error...
This suggests that our dbt cli profile block, which we have defined in dbt Cloud, does not have a name or target or target_configs, but it does..
```pydantic.error_wrappers.ValidationError: 3 validation errors for DbtCoreOperation
dbt_cli_profile -&gt; name
  field required (type=value_error.missing)
dbt_cli_profile -&gt; target
  field required (type=value_error.missing)
dbt_cli_profile -&gt; target_configs
  field required (type=value_error.missing)```
I was able to use the `profile_dir` parameter to use my local credentials, but this only verifies there aren't obvious problems with the flow code.

`prefect-dbt==0.3.1`
`prefect-snowflake==0.26.0`

Any ideas?

image.png

I think I found the problem.  It looks like the <https://prefecthq.github.io/prefect-dbt/cli/commands/|documentation> is incorrect.
From the docs
```snowflake_connector = await SnowflakeConnector.load("snowflake-connector")
target_configs = SnowflakeTargetConfigs(connector=snowflake_connector)
dbt_cli_profile = DbtCliProfile(
    name="jaffle_shop",
    target="dev",
    target_configs=target_configs,
)
profile = dbt_cli_profile.get_profile()
dbt_init = DbtCoreOperation(
    commands=["dbt debug", "dbt list"],
    dbt_cli_profile=dbt_cli_profile,
    overwrite_profiles=True
)
dbt_init.run()```
Specifically `profile = dbt_cli_profile.get_profile()`  is wrong.

DbtCoreOperation uses `get_profile()` internally, so we shouldn't use it before passing the profile in.

cc: <@U04JTAL3LEB>

<@U02JKLM1C2K> I'm sending a support email to ask for a fix, but where would I do this without the support email.

Hey <@U01617HFQQK>!! We'll follow up in the support case, but typically bugs/doc correction issues can be filed on the <https://github.com/PrefectHQ/prefect-dbt/issues|prefect-dbt git repo>.

<@U01617HFQQK> without seeing exactly the errors you were getting, I think I was able to recreate the issue.  I'll create a github issue and work on a PR. Thanks for spotting this!

<@U03D3KHGC0L>, I couldn't find where the docs were at in the repo and didn't want to spend too long figuring it out.

<@U01617HFQQK> I believe the docs are generated automatically from the Docstrings of the classes and functions in that repo, so I believe <https://github.com/PrefectHQ/prefect-dbt/blob/4bfdda85940140eb640b2d7c50a8a3e3d5f01f90/prefect_dbt/cli/commands.py#L212|this line> would have to be changed. I have created a <https://github.com/PrefectHQ/prefect-dbt/pull/143|PR here> from a fork, feel free to add anything I missed.

Thanks!  I'll open a PR that way next time.