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

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2016/11/15 00:28:02 UTC

[jira] [Updated] (JCLOUDS-601) Allow RunScriptOptions to specify timeout to override global timeout

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

Ignasi Barrera updated JCLOUDS-601:
-----------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.1.0

> Allow RunScriptOptions to specify timeout to override global timeout
> --------------------------------------------------------------------
>
>                 Key: JCLOUDS-601
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-601
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 2.1.0
>
>
> Currently, script execution timeouts are only configurable globally - you can't specify it on a case-by-case basis without reinstantiating the whole compute service. It'd be awfully nice to be able to specify this in RunScriptOptions and override the global timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)