Answers inline. From: Jessica Wang <jessica.w...@citrix.com<mailto:jessica.w...@citrix.com>> Date: Tuesday 8 October 2013 5:10 PM To: "<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Cc: Alena Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>, Nitin Mehta <nitin.me...@citrix.com<mailto:nitin.me...@citrix.com>>, Shweta Agarwal <shweta.agar...@citrix.com<mailto:shweta.agar...@citrix.com>> Subject: questions about registerIso API and updateIsoPermissions API
Hi, I have questions about registerIso API and updateIsoPermissions API. (1) A normal user is allowed to specify isextractable property when registering an ISO (through registerIso API), but NOT allowed to update isextractable property when updating an ISO (through updateIsoPermissions API). Is this by design or it's just an API bug? Nitin>> This is a grey area. This was done for templates (Isos just inherited it) because derived templates may or may not belong to the same user and we want to follow the principle of least privilege. At the moment, I think that for Isos we should allow to edit it so would call it an API bug. (2) A normal user is NOT allowed to specify isfeatured property when registering an ISO (through registerIso API), but allowed to update isfeatured property when updating an ISO (through updateIsoPermissions API)? Is this by design or it's just an API bug? Nitin>> Register Iso does provide an option to mark an ISO featured. I see that in the latest master. Jessica
