[
https://issues.apache.org/jira/browse/AMBARI-18687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603730#comment-15603730
]
Hadoop QA commented on AMBARI-18687:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12835047/rb53158.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 1 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
ambari-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8997//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8997//console
This message is automatically generated.
> Ambari-agent: CLI utility to support storing passwords using hadoop
> credential store
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-18687
> URL: https://issues.apache.org/jira/browse/AMBARI-18687
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
> Affects Versions: 2.4.2
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53158.patch
>
>
> Some components support the use of Hadoop Credential Store API to read
> passwords from a JCEKS provider. If this is enabled, ambari agent must be
> able to use the JCEKS provider to store passwords.
> This requires writing a command line wrapper utility over the Hadoop
> Credential Provider API in Java on the ambari agent side. Whenever a
> non-status command is received, ambari agent will use this utility to create
> the JCEKS provider for each configuration with the passwords in them.
> After that, the configuration XML files will be generated using the path to
> their respective JCEKS provider path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
