Closed (fixed)
Project:
Tugboat QA API
Version:
7.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
29 Mar 2019 at 15:55 UTC
Updated:
15 Apr 2019 at 20:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
nerdsteinOne "easy" thing to consider is just writing output to a passed file path.
https://cgit.drupalcode.org/tugboat/tree/tugboat.module#n123
I'm concerned how this might impact the other streams but I think testing is needed.
Approach motivated by https://askubuntu.com/questions/420981/how-do-i-save-terminal-output-to-...
Comment #3
nerdsteinIn general, the approach "worked". But, it's not complete. So, I'll hold off on the patch.
The output generated is only the JSON response output from the command. The console output and/or errors are captured as other streams. Such things are also value for logging purposes.
This approach needs extended for both streams and output. I'm recommending three new, optional parameters for the file paths of stdout, errors, and the command output.
Comment #4
nerdsteinComment #5
daggerhart commentedThis looks reasonable to me. It's hard for me to know for sure without a way to test it, but what I am seeing in the patch looks right.
Comment #6
nerdsteinAwesome, merging
Comment #8
nerdsteinFixed