[jira] [Commented] (CLOUDSTACK-2091) API Removed Response Parameters for deleteUser, addTrafficMonitor, listTrafficMonitors

["Min Chen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635315#comment-13635315 ] 

Min Chen commented on CLOUDSTACK-2091:
--------------------------------------

I compared TrafficMonitorResponse class from 4.1 branch and 4.0 branch, and they are exactly the same, only have the following response parameters: id, zoneId, ipAddresses, numRetries, timeout, didn't see anything mentioned in the bug (privateinterface, privatezone, publicinterface, publiczone, usageinterface, username). Joe, can you please clarify how you got those difference?
                
> API Removed Response Parameters for deleteUser, addTrafficMonitor, listTrafficMonitors
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2091
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2091
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.1.0
>            Reporter: Joe Brockmeier
>            Assignee: Min Chen
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> It looks like the response parameters have changed for three API commands in 4.1.0.  The following response parameters are not being documented as part of the response objects for these calls:
> - deleteUser: id, account, accountid, accounttype, apikey, created, domain, domainid, email, firstname, lastname, secretkey, state, timezone, username
> - addTrafficMonitor: privateinterface, privatezone, publicinterface, publiczone, usageinterface, username
> - listTrafficMonitor: privateinterface, privatezone, publicinterface, publiczone, usageinterface, username
> Is this acceptable? My understanding was that the API shouldn't change in terms of removing expected parameters between 4.x releases. 

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