cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3975) createVolume using accountid
Date Wed, 08 Feb 2017 09:23:59 GMT

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

Daan Hoogland closed CLOUDSTACK-3975.
-------------------------------------
    Resolution: Won't Fix

> createVolume using accountid
> ----------------------------
>
>                 Key: CLOUDSTACK-3975
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3975
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.1.0
>         Environment: Any environment
>            Reporter: Mitchell Klijnstra
>            Priority: Minor
>              Labels: API
>
> Currently it is possible when calling the CS API to associate a new yet-to-create volume
to an account using the account name. This works but is in my opinion not as strict as having
the ability to use an account' UUID instead. This would make sure that the disk is never created
under a different account then was intended.
> It seems logically to me to also allow UUID's as this seems to be the general practise
on the API as a whole. Consistency being key.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message