Hi,
Switching to a POST gives a 200 with the user JSON returned though this
does not include any quota information back. I am guessing this is a
bug and will start a ticket for it, unless you think I am doing
something wrong here.
{u'display_name': u' Mr. Test', u'keys': [{u'access_key': u'REDAC
On Tue, Apr 22, 2014 at 7:51 AM, Derek Yarnell wrote:
> Hi Yehuda,
>
> So i finally got to testing the quota stuff per the info from lines
> 712-758 in rgw_rest_user.cc. I am using the query parameters version
> and getting a 409 error out. Below in the debug log of the gateway
> running 0.79.
>
Hi Yehuda,
So i finally got to testing the quota stuff per the info from lines
712-758 in rgw_rest_user.cc. I am using the query parameters version
and getting a 409 error out. Below in the debug log of the gateway
running 0.79.
2014-04-22 10:46:56.852360 7fa46bfff700 20 enqueued request
req=0
Derek,
I have some. I'll get them by the end of the week at the latest.
On Mon, Apr 7, 2014 at 4:52 PM, Yehuda Sadeh wrote:
> On Mon, Apr 7, 2014 at 4:34 PM, Derek Yarnell
> wrote:
> > Hi,
> >
> > Most likely Yehuda can speak to this. So there is some documentation on
> > the way to set quot
On Mon, Apr 7, 2014 at 4:34 PM, Derek Yarnell wrote:
> Hi,
>
> Most likely Yehuda can speak to this. So there is some documentation on
> the way to set quotas for a user in master (src/rgw/rgw_rest_user.cc
> line 712) but these are not in the docs it seems yet. I have started to
> incorporate the
