-
Notifications
You must be signed in to change notification settings - Fork 6
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
Make run_result.json
parsable even in case of task execution error
#80
Comments
Hi, Can I work on this issue ? Thanks, |
Of course @balaaparna-dev! I assigned it to you, thanks to looking into it. |
Hi @balaaparna-dev, Are there any updates on progress of this issue? |
Hi @balaaparna-dev, As there hasn't been any progress or updates on this, I'll unassign you for now. However, if you do open a PR, it will be reviewed, and you'll be reassigned if no one else handles it in the meantime. Thanks for all the efforts so far! 🍀 |
Feature description
Users want to send notifications of corresponding error dbt models but can't as the
run_results. json
can't be parsed from outputs (task execution in error state doesn't expose outputs properties).One workaround is to make the task fails silently (
dbt --log-format-file json build --select <MODEL NAME> --target prod 2>/dev/null || true
) and direct the stderr to the null device and add an OR condition with true, making the flow always return a successful run, then parse my run_results.json and potentially add a block ofio.kestra.core.tasks.executions.Fail
if detect an errorThe text was updated successfully, but these errors were encountered: