You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2016/06/30 18:02:10 UTC

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

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

Sumit Mohanty updated AMBARI-17507:
-----------------------------------
    Attachment: AMBARI-17507.patch

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