[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260564#comment-15260564
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-215165382
@mlsorensen
- presently, setting bitmask to 0 in commands.properties does not disable
the API but that no roles would have that API; though if an API through its
`authroized` annotation enables itself for a roletype that will be considered
- this feature implements a DENY rule that is checked before annotations
are checked to provide a mechanism to disable an API (or group of APIs if a
wildcard rule is used) that could have been enabled by the annotation (for
example)
@koushik-das
- Existing users are not migrated automatically, they continue to use
static-checker
- Commands.properties file is only removed from codebase, after an upgrade
this file won't be removed by the deb/rpm packages
- New users and installations are no longer encouraged to use the old
static-checker, therefore with the aim of deprecating the static-checker over
time dynamic-checker is enabled by default
- Any change can introduce side-effects and bugs but that does not mean we
should stop innovating or stop improving cloudstack; such an attitude would be
harmful for any project
- I really appreciate your code review, improvement suggestions and testing
feedback instead, on this PR. Thanks.
> 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)
