[jira] [Commented] (AMBARI-17507) Provide an option not to log ambari-agent command output for user custom script action

2016-07-02 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-17507:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5209 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5209/])
AMBARI-17507. Provide an option not to log ambari-agent command output 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8d83ea62c689d556dd104fcb624ca4537a796b53])
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* ambari-agent/src/main/python/ambari_agent/ActionQueue.py
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java


> Provide an option not to log ambari-agent command output for user custom 
> script action
> --
>
> Key: AMBARI-17507
> URL: https://issues.apache.org/jira/browse/AMBARI-17507
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17507.patch
>
>
> Custom commands is a way to create a set of commands that can perform 
> specific actions on the cluster. Class of actions typically involve 
> initialization, setup, and cleanup - different than the 
> start/stop/configure/install etc.
> By default all command output gets logged. It should be possible for the 
> command to indicate if the output should be logged if the command may output 
> PII information.



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


[jira] [Commented] (AMBARI-17507) Provide an option not to log ambari-agent command output for user custom script action

2016-06-30 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-17507:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12815514/AMBARI-17507.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 
ambari-server.

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

This message is automatically generated.

> Provide an option not to log ambari-agent command output for user custom 
> script action
> --
>
> Key: AMBARI-17507
> URL: https://issues.apache.org/jira/browse/AMBARI-17507
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17507.patch
>
>
> Custom commands is a way to create a set of commands that can perform 
> specific actions on the cluster. Class of actions typically involve 
> initialization, setup, and cleanup - different than the 
> start/stop/configure/install etc.
> By default all command output gets logged. It should be possible for the 
> command to indicate if the output should be logged if the command may output 
> PII information.



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


[jira] [Commented] (AMBARI-17507) Provide an option not to log ambari-agent command output for user custom script action

2016-06-30 Thread Sumit Mohanty (JIRA)

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

Sumit Mohanty commented on AMBARI-17507:


Adding support for a parameter "log_output" that can be set to true or false.

> Provide an option not to log ambari-agent command output for user custom 
> script action
> --
>
> Key: AMBARI-17507
> URL: https://issues.apache.org/jira/browse/AMBARI-17507
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
>
> Custom commands is a way to create a set of commands that can perform 
> specific actions on the cluster. Class of actions typically involve 
> initialization, setup, and cleanup - different than the 
> start/stop/configure/install etc.
> By default all command output gets logged. It should be possible for the 
> command to indicate if the output should be logged if the command may output 
> PII information.



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