[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260615#comment-15260615
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user jburwell commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-215171740
@koushik-das I don't understand how adoption of this feature differs from
any other feature. A user deploys the release into a test/pilot environment
and determine whether or not it they wish to migrate to it. To be clear,
existing users are **not** automatically migrated.
Per the FS, this feature alows the definition of custom roles as you
describe. For backwards compatibility, all roles must be mapped to one of the
four types.
I don't understand your point about someone writing a plugin to allow
custom roles. This PR is exactly the plugin you describe.
> 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)
