I also updated the version of the dbt image (which is only used for serving dbt docs) to keep it in line with the version running in the airflow scheduler. Maybe if I adopt a CeleryExecutor or K8sExecutor setup, I'll just fold dbt doc-serving into worker or executor image and eliminate the dbt_proj service.
I also updated the version of the dbt image (which is only used for serving dbt docs) to keep it in line with the version running in the airflow scheduler. Maybe if I adopt a CeleryExecutor or K8sExecutor setup, I'll just fold dbt doc-serving into worker or executor image and eliminate the
dbt_projservice.