incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-2650) Secure configurations should be tagged with a prefix secure.
Date Mon, 15 Jul 2013 23:12:51 GMT
Jaimin D Jetly created AMBARI-2650:
--------------------------------------

             Summary: Secure configurations should be tagged with a prefix secure.
                 Key: AMBARI-2650
                 URL: https://issues.apache.org/jira/browse/AMBARI-2650
             Project: Ambari
          Issue Type: Improvement
          Components: client
    Affects Versions: 1.2.5
            Reporter: Jaimin D Jetly
            Assignee: Jaimin D Jetly
             Fix For: 1.3.0


* Right now we tag every configuration with prefix "version" like _version1373590307538_.
* Web-ui should check for security_enabled flag before applying configurations to the cluster
and tag it as _secure_version1373590307538_ if security is enabled.
* This helps to identify type of configuration (secure or unsecure) while getting a list of
configurations via API: http:<ambari server hostname>:8080/api/v1/clusters/c1/configurations
 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message