You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@libcloud.apache.org by Jay Doane <ja...@gmail.com> on 2010/05/20 01:26:37 UTC

[libcloud] Why don't ScriptDeployments have exit status?

Having access to ScriptDeployment.stdout and .stderr has been crucial  
for debuggin complicated scripts, but I was curious why that class  
doesn't also expose an exit status as well?

Thanks,
Jay

Re: [libcloud] Why don't ScriptDeployments have exit status?

Posted by Paul Querna <pa...@querna.org>.

Added in r946494:
http://svn.apache.org/viewvc?view=revision&revision=946494

Thanks for the idea!

On Wed, May 19, 2010 at 4:59 PM, Paul Querna <pa...@querna.org> wrote:
> On Wed, May 19, 2010 at 4:26 PM, Jay Doane <ja...@gmail.com> wrote:
>> Having access to ScriptDeployment.stdout and .stderr has been crucial for
>> debuggin complicated scripts, but I was curious why that class doesn't also
>> expose an exit status as well?
>
> Good Idea, Logged this as:
> https://issues.apache.org/jira/browse/LIBCLOUD-37
>
> think it should just take exposing the right variables from paramiko?
>

Re: [libcloud] Why don't ScriptDeployments have exit status?

Posted by Paul Querna <pa...@querna.org>.

On Wed, May 19, 2010 at 4:26 PM, Jay Doane <ja...@gmail.com> wrote:
> Having access to ScriptDeployment.stdout and .stderr has been crucial for
> debuggin complicated scripts, but I was curious why that class doesn't also
> expose an exit status as well?

Good Idea, Logged this as:
https://issues.apache.org/jira/browse/LIBCLOUD-37

think it should just take exposing the right variables from paramiko?