cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <>
Subject RE: Question: deprecated
Date Thu, 12 May 2016 06:00:17 GMT
Hi Mike and Will,

I'll update the admin-docs PR on this, if you take a look at the dynamic roles FS it has pointers
on how to deal with new API, what are role types (RoleType has existed since at least 4.3)

In short use the authorized field in the APICommand annotation to set default authorization
for a role type. The annotation has existed as old as 4.2/4.3 but it's not quite popular.
In addition to this, all release notes should include new APIs so admins if they wish can
disable any APIs enabled for a role type.

For example, if you want your new APIs to be enabled user roles you can set: authorized= {RoleType.User}.
Similarly, to enable for all, you can set it to: authorized= {RoleType.Admin, RoleType.ResourceAdmin,
RoleType.DomainAdmin, RoleType.User}.



Rohit Yadav
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

-----Original Message-----
From: [] On Behalf Of Will Stevens
Sent: Wednesday, May 11, 2016 9:18 PM
Subject: Re: Question: deprecated

I think this is the extent of the documentation at this point.

Rohit, maybe you can shed some light on this from a developer's perspective and how we should
be handling this going forward?  Are there official docs which covered how to use ''?
 If so, we should update them to reflect this new feature...

Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w *|* tw @CloudOps_

On Wed, May 11, 2016 at 10:40 AM, Tutkowski, Mike <
> wrote:

> Hi,
> I see in afcbd27 that we've deprecated
> Is there documentation on the new way that we specify permissions for 
> a given API these days?
> Thanks!
> Mike
View raw message