Closed mroy-seedbox closed 1 month ago
Thanks for reaching out @mroy-seedbox !
Sorry to redirect you, but could you please submit this to the dbt Cloud support team via the "Create a support ticket" or "Leave feedback" button in dbt Cloud or by emailing support@getdbt.com?
I'd also recommend linking to this GitHub issue in your description.
Since this is specific to dbt Cloud and not dbt Core, I'm going to close this issue as "not planned" for the dbt-core repo.
@dbeatty10: This might also be fixable in dbt Core by running dbt deps
without parsing dbt_project.yml
(if that is sensible, but idk if there are any dependencies between the two).
Actually, looks like this is a duplicate of #8913.
It would be nice to see a fix for it, just like it was also fixed for env vars in #2368, and for profiles in #4554.
@mroy-seedbox re-opened https://github.com/dbt-labs/dbt-core/issues/8913 per request 👍
Is this a new bug in dbt-core?
No, it is a bug/limitation in dbt Cloud. I think it has pretty much always been there, but we just ran into it.
Current Behavior
When a variable is mandatory in
dbt_project.yml
(no default value is provided), runs in dbt Cloud fail because the variable is not provided whendbt deps
is run forcibly.We do not use packages, so we never run
dbt deps
locally. And if we did run it, we would be able to provide the variables.Expected Behavior
Have the ability to disable
dbt deps
, or even better yet: not run that step at all if nopackages.yml
file is present!Or have the ability to specify variables for
dbt deps
.... but that would mean running it ourselves in our job steps, rather than having it run automatically.Steps To Reproduce
In
dbt_project.yml
, add something like this:In dbt cloud, all jobs will fail when running
dbt deps
:Environment