dbt Cloud Provider Not Compatible with emea.dbt.com #27146
Comments
|
Hey @ernestoongaro Thanks for submitting this issue! It looks like you've checked that you're willing to submit a PR, that would be much appreciated! Would you like me to assign this task to you? |
|
@o-nikolas I can take this. |
Thanks Josh! |
Closes: apache#27146 Currently users can connect to both single-tenant and multi-tenant instances of dbt Cloud. However, for the enterprise tier, there is a new region offered as well as private instance support. The existing `tenant` value does not cover the ability to modify the entire domain name which could be required for users on the enterprise plan. This enhancement allows users to specify the tenant domain they wish to connect to while keeping the "cloud.getdbt.com" domain as the default. Additionally, backward compat is implemented for those who are only specifying the third-level domain for single-tenant instances and wish to upgrade the provider version.
Closes: #27146 Currently users can connect to both single-tenant and multi-tenant instances of dbt Cloud. However, for the enterprise tier, there is a new region offered as well as private instance support. The existing `tenant` value does not cover the ability to modify the entire domain name which could be required for users on the enterprise plan. This enhancement allows users to specify the tenant domain they wish to connect to while keeping the "cloud.getdbt.com" domain as the default. Additionally, backward compat is implemented for those who are only specifying the third-level domain for single-tenant instances and wish to upgrade the provider version.
Related: apache/airflow#27146 apache/airflow#28890 In OSS Airflow, the dbt Cloud connection has replaced `schema` for `host` to provide the "tenant" name. This fix was included in the latest version of the dbt Cloud provider (2.3.1) and should also be reflected in this provider.
Related: apache/airflow#27146 apache/airflow#28890 In OSS Airflow, the dbt Cloud connection has replaced `schema` for `host` to provide the "tenant" name. This fix was included in the latest version of the dbt Cloud provider (2.3.1) and should also be reflected in this provider.
|
hey all @josh-fell @ernestoongaro, Looks like this fix hasn't been released yet. Thanks, |
|
@erdinculuturk-nw The fix was released as part of version 2.3.1 of the dbt Cloud provider package. What version of the provider package do you have installed? |
|
Hey @josh-fell, thanks for the quick reply. |
|
Right on, if you still can't connect to the EMEA region with 2.3.1+, let us know. |
|
hey @josh-fell, just wanted to let you know that it works fine now after upgrading to proper versions for both Airflow and dbt Cloud provider. |
Apache Airflow Provider(s)
dbt-cloud
Versions of Apache Airflow Providers
No response
Apache Airflow version
2.3.3
Operating System
Linux
Deployment
Composer
Deployment details
No response
What happened
Trying to use the provider with dbt Cloud's new EMEA region (https://docs.getdbt.com/docs/deploy/regions) but not able to use the emea.dbt.com as a tenant, as it automatically adds
.getdbt.comto the tenantWhat you think should happen instead
We should be able to change the entire URL - and it could still default to cloud.getdbt.com
How to reproduce
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: