cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-5872) Async response from addAccountToProject doesn't contain useful information
Date Mon, 03 Mar 2014 20:59:24 GMT

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

Alena Prokharchyk reopened CLOUDSTACK-5872:
-------------------------------------------


Reopening the bug. I've reverted the commit as it breaks API compatibility. We can't just
change the response format because it breaks API backwards compatibility. Third party developers
integrating with our API, are gonna have broken apps due to this. 

David, please close the bug. I understand that the API response format might not be ideal,
but you can always get more descriptive result when execute corresponding list* command. So
first you get true/false in the response. And if you need some additional info, you need to
execute the list* command.

> Async response from addAccountToProject doesn't contain useful information
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5872
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5872
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>            Reporter: Bill Jones
>            Assignee: David Grizzanti
>             Fix For: 4.4.0
>
>         Attachments: unnamed.patch
>
>
> The async response from addAccountToProject doesn't contain useful information. Generally
async responses for commands that modify resources include the resource ID and/or description
in the async response. This is not true of addAccountToProject or deleteAccountFromProject.
Consequently the response is not so useful to clients that do not have access to the context
of the request. Also, it seems inconsistent with the general design of the API.



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

Mime
View raw message