cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mandar Barve (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-6213) Add new field to API @Parameter indicating if the param should be skipped from logs
Date Wed, 12 Mar 2014 04:12:43 GMT

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

Mandar Barve reassigned CLOUDSTACK-6213:
----------------------------------------

    Assignee: Mandar Barve

> Add new field to API @Parameter indicating if the param should be skipped from logs
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6213
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6213
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.4.0
>            Reporter: Alena Prokharchyk
>            Assignee: Mandar Barve
>             Fix For: Future
>
>
> There are 2 parameters in @Apicommand:
> requestHasSensitiveInfo
> responseHasSensitiveInfo
> If set to true, the command will go through validation and certain parameters will be
skipped from logging. Today these parameters are hardcoded. We have to introduce a generic
way of marking this parameters as "excluded from logging". New field should be added to @Parameter
for this purpose.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message