Surfacing of DBT Cloud Logs to the logs of the DBTCloudRunJobOperator
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 484
Description
### Description
Currently if a DBT Cloud Job triggered by the DBT Cloud Job Operator fails. The airflow task which uses the operator will fail and error but it will not get the logs from DBT Cloud so we are aware of why it failed.
### Use case/motivation
Easier developer experience when debugging tasks. Helps remove extra steps when seeing why a DAG has failed.
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start at the DBTCloudRunJobOperator and trace how a failed DBT Cloud job is reported to the Airflow task. Verify the failure path and its tests, then confirm that the Airflow task logs include the DBT Cloud failure logs needed for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100