Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve dbt command execution logs to troubleshoot
None
values (#1392)
Recently, an Astronomer customer reported they were facing the following error while trying to run Cosmos and couldn't troubleshoot it (the screenshot was a courtesy by the customer, when using Cosmos 1.7.1): ![type-error](https://github.com/user-attachments/assets/bfb15103-d6f8-425c-ae0e-25b40953d3d7) The following log line was sub-optimal since it errored if the value was None: https://github.com/astronomer/astronomer-cosmos/blob/43998d246661b0f27580cf9f314d19aeef785b6a/cosmos/dbt/graph.py#L136 To change just the log line was not enough since the `None` would also break the subprocess command execution (screenshot also by the customer when trying 1.8.0a1): ![type-error-2](https://github.com/user-attachments/assets/d8980b4e-eed1-4948-825f-3f219e84b1ee) By changing both, the source problem became evident to the customer (screenshot by the customer when trying 1.8.0a2): ![unable-to-run](https://github.com/user-attachments/assets/80906ee0-8c17-4615-8ca2-b87a704db5e1)
- Loading branch information