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

Posted to dev@libcloud.apache.org by "Paul Querna (JIRA)" <ji...@apache.org> on 2010/05/20 02:00:54 UTC

[libcloud] [jira] Created: (LIBCLOUD-37) ScriptDeployment should expose exit status

ScriptDeployment should expose exit status
------------------------------------------

                 Key: LIBCLOUD-37
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-37
             Project: Libcloud
          Issue Type: Improvement
            Reporter: Paul Querna


feature request from Jay Doane:

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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[libcloud] [jira] Resolved: (LIBCLOUD-37) ScriptDeployment should expose exit status

Posted by "Paul Querna (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/LIBCLOUD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Querna resolved LIBCLOUD-37.
---------------------------------

    Resolution: Fixed

Added in r946494

> ScriptDeployment should expose exit status
> ------------------------------------------
>
>                 Key: LIBCLOUD-37
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-37
>             Project: Libcloud
>          Issue Type: Improvement
>            Reporter: Paul Querna
>
> feature request from Jay Doane:
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.