jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-220) Add project id to relevant CloudStack API options
Date Fri, 02 Aug 2013 00:17:49 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727143#comment-13727143
] 

ASF subversion and git services commented on JCLOUDS-220:
---------------------------------------------------------

Commit 2fcd90c394c8d113f9b78dde675f040c8892407a in branch refs/heads/master from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=2fcd90c ]

JCLOUDS-220. Adding projectId to a bunch of CloudStack API options

                
> Add project id to relevant CloudStack API options
> -------------------------------------------------
>
>                 Key: JCLOUDS-220
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-220
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 1.6.1
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.7.0, 1.6.2
>
>
> There are a number of places where CloudStack APIs can take project IDs as parameters
where we don't currently support that. This should be fixed pretty easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message