[
https://issues.apache.org/jira/browse/AMBARI-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000656#comment-15000656
]
Hadoop QA commented on AMBARI-13814:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771739/AMBARI-13814_trunk_02.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4256//console
This message is automatically generated.
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
