Lightdash CLI currently depends on the dbt core but dbt cloud users use dbt cloud CLI instead of dbt core.
dbt cloud CLI support nearly all of the core commands - you can see the list here.
Our CLI currently depends on the commands: dbt ls, dbt --version, dbt compile
The main blocker at the time is when we check the version of the command dbt --version where the code expects something like '1.5.0' but with dbt cloud CLI it is different.
To solve:
Is there a way for us to relate the dbt cloud CLI version to a dbt core version? if so, this could be a quick fix.
-- Update --
There isn't.
To make this work we need to change our code to stop picking a manifest schema version based on the dbt-core version. We need to get the manifest version from the manifest object that the cli outputs.
Check this slack thread for more detail https://lightdash.slack.com/archives/C03MNR8L51C/p1708442245954929
Description
Lightdash CLI currently depends on the dbt core but dbt cloud users use dbt cloud CLI instead of dbt core.
dbt cloud CLI support nearly all of the core commands - you can see the list here.
Our CLI currently depends on the commands: dbt ls, dbt --version, dbt compile
The main blocker at the time is when we check the version of the command
dbt --version
where the code expects something like '1.5.0' but with dbt cloud CLI it is different.To solve: Is there a way for us to relate the dbt cloud CLI version to a dbt core version? if so, this could be a quick fix.
-- Update -- There isn't. To make this work we need to change our code to stop picking a manifest schema version based on the dbt-core version. We need to get the manifest version from the manifest object that the cli outputs. Check this slack thread for more detail https://lightdash.slack.com/archives/C03MNR8L51C/p1708442245954929
Workaround:
"How do I run both the dbt Cloud CLI and dbt Core?"
What problem does this solve?