-
Notifications
You must be signed in to change notification settings - Fork 124
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
Hook to be called after cosmos task execution #976
Comments
Thanks a lot, @SiddiqueAhmad , for writing down this! Giving further context, this came from a discussion in Slack #airflow-dbt: https://apache-airflow.slack.com/archives/C059CC42E9W/p1715857421750369 It is a valid use case, and we don't have an out-of-the-box solution at the moment. Similar to how we're handling astronomer-cosmos/cosmos/operators/local.py Line 592 in af11d34
We could have a mechanism for users to define a function that would be called after Cosmos tasks are executed and that could receive the result/context. I believe, ideally, this function would affect all (at least Local/VirtualEnv) Cosmos Operators. This may solve the problem described in #903. Did you check with your team if someone would be available/interested in implementing this, @SiddiqueAhmad ? |
To pipe dbt test results.json, We need to register hook with results so users can use it for further integration. We need this for integration with openmetadata for data quality.
The text was updated successfully, but these errors were encountered: