Chip,
The downside of using listApis to detect whether an API command is being
exposed is that an error will appear in the log (not on UI)
/client/api?command=listApis&name=listVmwareDcs
{
"listapisresponse": {
"uuidList": [],
"errorcode": 530,
"cserrorcode": 9999,
"errortext": "Api Discovery plugin was unable to find an api by that
name or process any apis"
}
}
Jessica
-----Original Message-----
From: Jessica Wang
Sent: Friday, September 06, 2013 1:58 PM
To: 'Chip Childers'
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com;
Sateesh Chodapuneedi
Subject: RE: Questions about 4.2 RC - listVmwareDcs API - Here's the discovery
API
Chip,
I just tested listApis and it worked! ^_^
Yes, this is enough and I'll change UI to use listApis to determine whether to
call listVmwareDcs API in zone detail page.
Thanks!
Jessica
-----Original Message-----
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Friday, September 06, 2013 1:49 PM
To: Jessica Wang
Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com;
Sateesh Chodapuneedi
Subject: Re: Questions about 4.2 RC - listVmwareDcs API
On Fri, Sep 06, 2013 at 08:21:38PM +0000, Jessica Wang wrote:
> > [Chip] Perhaps a future enhancement would be to use the discovery service
> > to figure out what API's are being exposed by the specific management
> > server, and adjust the UI accordingly.
>
> [Jessica] +1
> It will be great if server-side is able to provide this info (what API's are
> being exposed).
> Then, yes, UI can definitely be adjusted accordingly.
Here's the discovery API ->
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/listApis.html
I think this would be enough for the functionality we're talking about,
right?
