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

ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------

Github user swill commented on the pull request:

    https://github.com/apache/cloudstack/pull/1489#issuecomment-215479369
  
    In reading this, is it the case that if someone upgrades from a previous 
version to 4.9 (with this code included) they will not be able to take 
advantage of this functionality?  Maybe I did not understand those details 
correctly.  This is just a clarification so I know what to expect (I have 
customers who are interested in this functionality).
    
    @koushik-das Regarding: "Regarding writing a plugin, I meant that if 
someone really needed a functionality like this, they could have easily 
developed it outside of Cloudstack as well (like some kind of portal calling 
Cloudstack APIs)."  Given that I work a company who has done exactly that, I 
can assure you it is not "easy" and takes a huge development effort to recreate 
all the functionality provided by the ACS UI.  This is not really a viable 
option for people looking for this feature.
    
    @koushik-das I also don't understand this "Any blocker (including security 
bugs) in this will make the 4.9 release unusable for new installs as this the 
only authorisation mechanism for entering into the system.".  Can you explain 
what you mean?  How does this feature and a 'blocker bug' render 4.9 unusable?  
I am not quite following this.  Maybe someone else can also chime in to help 
explain his concerns.
    
    Thx...


> 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)

Reply via email to