[jira] [Commented] (AMBARI-8451) user and group properties should be created dynamically

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-8451:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12683708/AMBARI-8451.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/757//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/757//console

This message is automatically generated.

> user and group properties should be created dynamically
> -------------------------------------------------------
>
>                 Key: AMBARI-8451
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8451
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8451.patch
>
>
> For making a user or group properties appear in MISC tab with a user friendly name, it is required to have  definition of such properties in ambari-web configuration metadata i.e. in site_properties.js file.
> From 1.7.0 release such user/group properties are tagged with an attribute property_type as USER or GROUP by the API and so the definition of these properties can be prepared in the code dynamically by looking for such property_types. This will eliminate the need of adding a user or group definition every time a new service is introduced in a stack.



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