[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242761#comment-15242761
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user bhaisaab commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1489#discussion_r59855472
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/account/CreateAccountCmd.java
---
@@ -196,5 +204,8 @@ private void validateParams() {
if(StringUtils.isEmpty(getPassword())) {
throw new ServerApiException(ApiErrorCode.PARAM_ERROR, "Empty
passwords are not allowed");
}
+ if (getAccountType() == null && getRoleId() == null) {
--- End diff --
Fixed the roleId < 1L issue.
No, here the check is for maintaining backward compatibility. The
accounttype used to be a 'required' param, but now it's optional, and so is
'roleid'; this check is to ensure that at least one of the two are provided
> User Definable Roles
> --------------------
>
> Key: CLOUDSTACK-8562
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8562
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Paul Angus
> Assignee: Rohit Yadav
>
> Static command.properties moved to database and made user definable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
