Add ability to stream command output as a response (fixes conflict #443)

[lostsnow]

Just fix conflict pr #443, thanks @milolav

[manukall]

would it be possible to get this merged? we've got a long running command, and only see the output after everything finished. streaming the output would be really great.

[wille]

Much needed. Please merge.

[sto]

Any news about this PR? The feature would be quite useful.

[Ftrybe]

Any news about this PR?

[adnanh]

I'll try to test this out next week, and hopefully get it merged if I don't run into any issues :)

[adnanh]

Hmm, in order to get the streaming to work, I had to set these headers in the response as well:

 w.Header().Set("Content-Type", "text/event-stream")
 w.Header().Set("Cache-Control", "no-cache")
 w.Header().Set("Connection", "keep-alive")

Without those headers I observed command output not being streamed, but rather buffered & spit out after the connection is closed.

Do you think this header override is acceptable?

Another question, should we also stream the output to the logs in parallel, maybe even introduce a separate setting "include-command-output-in-the-logs" (or something less verbose)? :)

[Ftrybe]

I think it's reasonable to override the headers if streaming requires it. Additionally, an include-command-output-in-the-logs option would be useful, since not everyone might want to enable this feature

[Srijan-SS02]

@adnanh any updates on this PR? Need this feature urgently, please let know if you are merging it?