ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8451) user and group properties should be created dynamically
Date Wed, 26 Nov 2014 19:40:12 GMT

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

Hudson commented on AMBARI-8451:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit-docker #330 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/330/])
AMBARI-8451. user and group properties should be created dynamically (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=133381bac4ed3a8225c044eba663064299de65b4)
* ambari-web/app/controllers/main/admin/serviceAccounts_controller.js
* ambari-web/app/controllers/main/service/info/configs.js
* ambari-web/app/views/common/configs/services_config.js
* ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kdc-conf.xml
* ambari-web/test/utils/config_test.js
* ambari-web/test/mock_data_setup/configs_mock_data.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/data/site_properties.js
* ambari-web/app/data/HDP2/site_properties.js
* ambari-web/app/utils/config.js
* ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kadm5-acl.xml


> 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)

Mime
View raw message