[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266579#comment-15266579
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-216231216
I will make sure this gets into 4.9 because I think it is really needed.
We do need one more LGTM on the code. Also, since this PR does have some
implications regarding access to the system we should be pretty cautious. I am
pretty confident with a new install because that is what my CI has tested. I
think it would be prudent for us to do more testing of some upgrade scenarios
to make sure the code behaves as expected. I don't think this code should come
into play with upgrades because the old properties files should be ready, but I
think we need to validate the code behaves as expected. Has anyone tested this
yet?
I think we should be testing:
- Upgrading to 4.9 and NOT using this feature.
- Upgrading to 4.9 and running the `migrate-dynamicroles.py` script to
import the existing roles.
> 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)
