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) etc.
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}.
Regards.
Regards,
Rohit Yadav
[email protected]
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Will Stevens
Sent: Wednesday, May 11, 2016 9:18 PM
To: [email protected]
Subject: Re: Question: commands.properties.in deprecated
I think this is the extent of the documentation at this point.
https://github.com/apache/cloudstack-docs-admin/pull/37/files
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 'commands.properties.in'? If so, we should update them to
reflect this new feature...
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_
On Wed, May 11, 2016 at 10:40 AM, Tutkowski, Mike <[email protected]
> wrote:
> Hi,
>
>
> I see in afcbd27 that we've deprecated commands.properties.in.
>
>
> Is there documentation on the new way that we specify permissions for
> a given API these days?
>
>
> Thanks!
>
> Mike
>
