[
https://issues.apache.org/jira/browse/MESOS-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095472#comment-15095472
]
Marco Massenzio commented on MESOS-3035:
----------------------------------------
Thanks, [~karya].
There has actually been plenty of "activity" on the review itself - but that
ended up being discarded.
I think [~jieyu] has done something similar in another review (I have no longer
access to that email thread, I'm afraid) so he may be able to chime in.
For myself, I've implemented the ["wrapper"
class|https://github.com/massenz/execute-module/blob/develop/src/include/cmdexecute.hpp#L28]
for {{Subprocess}} in my own module, so the "boilerplate" has been eliminated.
As the original "reporter" for the issue, I'm happy for this to be closed as a
"won't fix" - or we can keep it "open" if others think it's still worth
pursuing in the future.
> As a Developer I would like a standard way to run a Subprocess in libprocess
> ----------------------------------------------------------------------------
>
> Key: MESOS-3035
> URL: https://issues.apache.org/jira/browse/MESOS-3035
> Project: Mesos
> Issue Type: Story
> Components: libprocess
> Reporter: Marco Massenzio
> Labels: mesosphere, tech-debt
>
> As part of MESOS-2830 and MESOS-2902 I have been researching the ability to
> run a {{Subprocess}} and capture the {{stdout / stderr}} along with the exit
> status code.
> {{process::subprocess()}} offers much of the functionality, but in a way that
> still requires a lot of handiwork on the developer's part; we would like to
> further abstract away the ability to just pass a string, an optional set of
> command-line arguments and then collect the output of the command (bonus:
> without blocking).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
