[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270137#comment-15270137
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-216749200
@jburwell The API is transactional and you're right if more than one admin
decide to change the order, client side final order checking will be needed.
This is also true for VPC ACL rules too, where the same sort of order is used
(it also supports draggable allow/deny items in the UI).
If I implement the API to apply change the order at once (instead of
multiple single operations) and there are multiple root admins changing the
rules, the order saved by the last user will be in effect; and client side
tracking/verification will still be required.
Realistically, only root admins will be using this feature and it's
unlikely to hit such a case often.
> 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)
