Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-24 Thread Darren Shepherd
The spring stuff doesn't help. This discussion didn't really go anywhere and there weren't much comments. I'd say at this point we just put together a proposal. Give me 5 minutes and I'll throw up a proposal in a different thread. Darren On Thu, Oct 24, 2013 at 1:47 PM, SuichII, Christopher w

Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-24 Thread SuichII, Christopher
I’d like to see if we can come up with some solution for this issue. Having ‘add these lines to commands.properties’ is not really an acceptable installation step for plugins/extensions/etc. So, the ideas I’ve seen are: -Turn commands.properties into a blacklist instead of a whitelist -Dynamical

Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-09 Thread SuichII, Christopher
I just wanted to add a little clarification from a plugin perspective. Having commands.properties as a whitelist just adds another place that plugins have to register with CloudStack. For plugins that do not intend on being a part of the CloudStack source, this is actually quite tricky. Currentl

Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-08 Thread Darren Shepherd
So I'm saying if you want to disable a command you put myBadCmd=0 in the commands.properties. So yes, a blacklist over a whitelist. For people paranoid about maybe some command exists that they don't know about, we can even add a "blacklist=false to the command properties. Then the commands.prope

Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-08 Thread SuichII, Christopher
Maybe we could consider switching from a whitelist to a blacklist, then. A whitelist is certainly easier in terms of a one-step configuration, but a blacklist would allow for much easier plugin development, installation and removal. Perhaps we could find write a script that generates the complet

RE: [DISCUSS] make commands.properties the exception, not the rule

2013-10-08 Thread Prachi Damle
I think commands.properties is not just providing ACL on the API - but it also serves as a whitelist of APIs available on the deployment. It can be a one-step configuration option to disable certain functionality. Prachi -Original Message- From: Darren Shepherd [mailto:darren.s.sheph..

Re: [DISCUSS] make commands.properties the exception, not the rule

2013-10-08 Thread Alena Prokharchyk
On 10/8/13 3:23 PM, "Darren Shepherd" wrote: >I would like to largely remove commands.properties. I think most API >commands naturally have a default ACL that should be applied. I think >it makes sense to add to the @APICommand flags for user, domain, >admin. Then, as an override mechanism, pe