No, dumb question of mine (the only type of question that is really dumb is one for a known answer)
It seems unlikely that it could have worked with a parameter with a conflicting name. If it didn't work at all before, we are fine. In the unlikely otherwise, we should make the api still accept the old parameter. On Fri, Aug 8, 2014 at 1:01 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > Pierre-Luc, > > Can you? > @Rohit: the old parameter is still accepted is it? > > On Fri, Aug 8, 2014 at 12:57 PM, Rohit Yadav (JIRA) <j...@apache.org> wrote: >> >> [ >> https://issues.apache.org/jira/browse/CLOUDSTACK-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Rohit Yadav closed CLOUDSTACK-6323. >> ----------------------------------- >> >> >> [~dahn] In the release notes we have to mention that this API has changed >> and will accept apikey by userapikey arg in the HTTP request. >> >>> GetUser API always returns admin info >>> ------------------------------------- >>> >>> Key: CLOUDSTACK-6323 >>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6323 >>> Project: CloudStack >>> Issue Type: Bug >>> Security Level: Public(Anyone can view this level - this is the >>> default.) >>> Components: API >>> Affects Versions: 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0 >>> Reporter: Chiradeep Vittal >>> Assignee: Rohit Yadav >>> Fix For: 4.4.1 >>> >>> >>> The annotation is API_KEY for the parameter apikey which automatically gets >>> set to the requesters api key instead of the requested API key. The >>> annotation should be USER_API_KEY instead. >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.2#6252) > > > > -- > Daan -- Daan
