[
https://issues.apache.org/jira/browse/CLOUDSTACK-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitchell Klijnstra updated CLOUDSTACK-3975:
-------------------------------------------
Description:
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.
was:
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 would of course
work but is in my opinion not as strict as having the ability to use a 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.
> 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 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
