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
cli: add the ability to output to /dev/stdout #2123
Labels
enhancement
New feature or request
Comments
jzorn
added a commit
to jzorn/bruno
that referenced
this issue
Apr 18, 2024
This change moves informational command outputs from console.log (prints on stdout) to console.warn/console.error (prints on stderr) to enable stdout processing in pipelines.
jzorn
added a commit
to jzorn/bruno
that referenced
this issue
Apr 18, 2024
This change moves informational command outputs from console.log (prints on stdout) to console.warn/console.error (prints on stderr) to enable stdout processing in pipelines.
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked the following:
Describe the feature you want to add
It is helpful to print the results of a collection run to stdout, as it is currently possible via
bru run --output /dev/stdout
. Some commands are adding additional output to stdout, e.g. when running a recursive collectionRunning Folder Recursively
. This output prevents output processing in a pipeline, e.g. viabru run --output /dev/stdout | jq
. By moving the non-result output to a different output stream, e.g. stderr, pipelines would be much easier to compose.Mockups or Images of the feature
The text was updated successfully, but these errors were encountered: