Hey @DataGobes ,
Thanks for sharing the workaround. Were you able to pass the DB_CLUSTER_ID to http_path in dbt profiles?
I am trying to construct the `http_path` in `profiles.yml` to mimic the all-purpose cluster pattern, sql/protocolv1/o/<workspace_id>/{{ env_var(‘DB_CLUSTER_ID’) }}.
It appears that `DB_CLUSTER_ID` is **not initialised at cluster warm-up** when using the native Databricks dbt task type, so this approach doesn’t work out of the box.
Please share your databricks job json and dbt_profile if possible.