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

Capture stderr/stdout output separately #6

Open
titpetric opened this issue Jul 12, 2024 · 0 comments
Open

Capture stderr/stdout output separately #6

titpetric opened this issue Jul 12, 2024 · 0 comments

Comments

@titpetric
Copy link
Owner

I may want to use taskfiles as an ETL pipeline API; it should be local filesystem aware, so it knows where to write out outputs if it's a "local" processing job (e.g. data extraction with parsing, jq, yq), however in some cases it makes sense to collect only the output directly (e.g. pipe workflow). Using CombinedOutput doesn't give us access to the stdout separately;

May want to reuse task-ui for this but adjust to capture the outputs separately, so i can distribute a job runner similar to a github matrix job, but sort of in a structured ETL framework.

Filing this in the idea pile, likely going to skip the distributed nature of some tasks 🗡️ ; but i'll need to fan out pretty soon as a single threaded job runner won't work for the use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant