Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dbt >= 1.6 breaks cosmos #444

Closed
harels opened this issue Aug 7, 2023 · 2 comments · Fixed by #564
Closed

dbt >= 1.6 breaks cosmos #444

harels opened this issue Aug 7, 2023 · 2 comments · Fixed by #564
Milestone

Comments

@harels
Copy link
Contributor

harels commented Aug 7, 2023

Kubernetes Airflow provider and dbt Core released new versions and these are breaking our build. We should look into this and address it.

@tatiana
Copy link
Collaborator

tatiana commented Sep 18, 2023

@harels does this issue relate to this PR: #426 ?

@tatiana tatiana added this to the 1.2.0 milestone Sep 23, 2023
harels pushed a commit that referenced this issue Sep 28, 2023
)

Cosmos tests broke when `dbt` 1.6 and
`apache-airflow-providers-cncf-kubernetes` 7.3.0 were released. There
was a quick fix, #426, so the CI wouldn't be red, but that meant we
didn't officially support the latest version of dbt if users wanted to
run both Cosmos and dbt in the same Python virtualenv.

This feature has been requested by a few community members via Airflow
Slack #airflow-dbt channel:
*
https://apache-airflow.slack.com/archives/C059CC42E9W/p1691652944543079?thread_ts=1691650827.900949&cid=C059CC42E9W
*
https://apache-airflow.slack.com/archives/C059CC42E9W/p1692396096001339

Closes: #444

This change was validated by:
* Running tests locally (Python 3.8 and Airflow 2.7)
* Creating a virtualenv with the latest versions
* Running the dags `basic_cosmos_dag` and `jaffle_shop_kubernetes`
@tatiana
Copy link
Collaborator

tatiana commented Oct 13, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants