Github user jburwell commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-214960750
@mlsorensen +1 -- well said. command.properties presents a number of
significant problems. First, in a clustered environment, it is possible (and
quite easy) for there to be inconsistent security policies across the cluster.
Second, command.properties does not permit the definition of new roles.
Limiting users to 4 roles in a modern cloud environment is a barrier to
CloudStack adoption.
As Marcus has stated, we can't move forward if we keep trying to maintain
outdated mechanisms. Existing users can continue to use command.properties and
migrate if/when they desire. New users gain the benefits of a more reliable
and flexible authorization implementation.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
