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

Hudson commented on AMBARI-13814:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3814 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3814/])
AMBARI-13814. Add (descriptive) label to permission resource and (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5a18b6b739b99c1d6c020369d6889613ad537103])
* ambari-server/docs/api/v1/permission-get.md
* ambari-server/docs/api/v1/permission-update.md
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PermissionResourceProviderTest.java
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/PermissionEntity.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/docs/api/v1/permission-delete.md
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* ambari-server/docs/api/v1/index.md
* ambari-server/docs/api/v1/permission-create.md
* ambari-server/docs/api/v1/permission-resources.md
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/docs/api/v1/permission-list.md
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PermissionResourceProvider.java


> Add (descriptive) label to permission resource and database schema
> ------------------------------------------------------------------
>
>                 Key: AMBARI-13814
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13814
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server, ambari-web
>    Affects Versions: 2.2.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: rbac
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13814_trunk_01.patch, 
> AMBARI-13814_trunk_02.patch, AMBARI-13814_trunk_03.patch
>
>
> Add (descriptive) label to permission resource and database schema to avoid 
> having to hardcode a descriptive name for a permission. For example:
> ||Permission Name||Permission Label||
> |VIEW.USER|View User|
> |CLUSTER.USER|Cluster User|
> |SERVICE.OPERATOR|Service Operator|
> |SERVICE.ADMINISTRATOR|Service Administrator|
> |CLUSTER.OPERATOR|Cluster Operator|
> |CLUSTER.ADMINISTRATOR|Cluster Administrator|
> This descriptive label can be used in user interfaces so that a descriptive 
> (or friendly) name does not have to be hardcoded. 
> {noformat:title=API Call Example}
> GET api/v1/permissions/1
> 200 OK
> {
>   "href" : "http://your.ambari.server/api/v1/permissions/1";,
>   "PermissionInfo" : {
>     "permission_id" : 1,
>     "permission_name" : "AMBARI.ADMIN",
>     "permission_label" : "Administrator",
>     "resource_name" : "AMBARI"
>   }
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to