Re: 44 API breakage in UpdateUser

2014-05-06 Thread Daan Hoogland
Ove, Can you create a patch with "git formaat-patch" from what you entered in the ticket, please? On Tue, May 6, 2014 at 8:02 PM, Ove Ewerlid wrote: > On 05/06/2014 08:45 AM, Antonio Fornié Casarrubios wrote: >> >> Hi Ove, >> >> Sorry but I think the only thing I did here was to put in a constan

Re: 44 API breakage in UpdateUser

2014-05-06 Thread Ove Ewerlid
On 05/06/2014 08:45 AM, Antonio Fornié Casarrubios wrote: Hi Ove, Sorry but I think the only thing I did here was to put in a constant a hardcoded value, but you should find who put the hardcoded value in the first place. yes, 'git blame' is lacking in conveying specifics. 'git log -p' provide

Re: 44 API breakage in UpdateUser

2014-05-05 Thread Antonio Fornié Casarrubios
Hi Ove, Sorry but I think the only thing I did here was to put in a constant a hardcoded value, but you should find who put the hardcoded value in the first place. Cheers Antonio 2014-05-06 0:44 GMT+02:00 Ove Ewerlid : > On 05/04/2014 10:19 PM, Ove Ewerlid wrote: > >> See https://issues.apach

Re: 44 API breakage in UpdateUser

2014-05-05 Thread Ove Ewerlid
On 05/04/2014 10:19 PM, Ove Ewerlid wrote: See https://issues.apache.org/jira/browse/CLOUDSTACK-6570 Suggested patch in comment. /Ove Looping in the person that 'git blame' thinks changed the value of API_KEY in ApiConstants the last time. Antonio, was USER_API_KEY introduced for cases wher