Skip to content
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

Open
Ben8t opened this issue Jan 11, 2024 · 0 comments
Open

Make run_result.json parsable even in case of task execution error #80

Ben8t opened this issue Jan 11, 2024 · 0 comments
Labels
area/plugin Plugin-related issue or feature request enhancement New feature or request good first issue Great issue for new contributors kind/customer-request Requested by one or more customers

Comments

@Ben8t
Copy link
Member

Ben8t commented Jan 11, 2024

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 of io.kestra.core.tasks.executions.Failif detect an error

@Ben8t Ben8t added the enhancement New feature or request label Jan 11, 2024
@anna-geller anna-geller added the kind/customer-request Requested by one or more customers label Jan 11, 2024
@anna-geller anna-geller added this to the v0.16.0 milestone Jan 11, 2024
@anna-geller anna-geller modified the milestones: v0.16.0, v0.17.0 Feb 12, 2024
@anna-geller anna-geller modified the milestones: v0.17.0, v0.22.0 Apr 10, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Issues Jun 10, 2024
@anna-geller anna-geller removed this from the v0.22.0 milestone Aug 20, 2024
@anna-geller anna-geller added the area/plugin Plugin-related issue or feature request label Aug 20, 2024
@tchiotludo tchiotludo added good first issue Great issue for new contributors and removed kind/good-first-issue labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin Plugin-related issue or feature request enhancement New feature or request good first issue Great issue for new contributors kind/customer-request Requested by one or more customers
Projects
Status: Backlog
Development

No branches or pull requests

3 participants