I honestly think no: not because it's not useful, but because dbt have the time and ability to maintain their own provider package, much like Great Expectations do:
https://greatexpectations.io/blog/airflow-operator/ I'd much rather we work with dbt to do what ever is needed to make it a full provider than pull it in tree when it already exists as a third party package. -ash On 3 March 2021 18:04:01 GMT, Ryan Hatter <ryannhat...@gmail.com> wrote: >Hey all, > >dbt <https://docs.getdbt.com/docs/introduction/> seems to continue to gain >momentum. There's already an airflow-dbt project ><https://github.com/gocardless/airflow-dbt> that is essentially a provider >package. Would it make sense to fold the dbt_hook ><https://github.com/gocardless/airflow-dbt/blob/master/airflow_dbt/hooks/dbt_hook.py> >and dbt_operator ><https://github.com/gocardless/airflow-dbt/blob/master/airflow_dbt/operators/dbt_operator.py> >into a provider package in the official airflow repo?
