On Thu, Dec 17, 2015 at 9:04 AM, Derek Yarnell wrote:
> I am having an issue with the 'radosgw-admin subuser create' command
> doing something different than the '/{admin}/user?subuser=json'
> admin API. I want to leverage subusers in S3 which looks to be possible
> in my
I am having an issue with the 'radosgw-admin subuser create' command
doing something different than the '/{admin}/user?subuser=json'
admin API. I want to leverage subusers in S3 which looks to be possible
in my testing for bit more control without resorting to ACLs.
radosgw-admin subuser create
On Thu, Dec 17, 2015 at 12:06 PM, Derek Yarnell wrote:
> On 12/17/15 2:36 PM, Yehuda Sadeh-Weinraub wrote:
>> Try 'section=user=cephtests'
>
> Doesn't seem to work either.
>
> # radosgw-admin metadata get user:cephtest
> {
> "key": "user:cephtest",
> "ver": {
>
On 12/17/15 2:36 PM, Yehuda Sadeh-Weinraub wrote:
> Try 'section=user=cephtests'
Doesn't seem to work either.
# radosgw-admin metadata get user:cephtest
{
"key": "user:cephtest",
"ver": {
"tag": "_dhpzgdOjqJI-OsR1MsYV5-p",
"ver": 1
},
"mtime": 1450378246,
On 12/17/15 1:09 PM, Yehuda Sadeh-Weinraub wrote:
>> Bug? Design?
>
> Somewhat a bug. The whole subusers that use s3 was unintentional, so
> when creating the subuser api, we didn't think of needing the access
> key. For some reason we do get the key type. Can you open a ceph
> tracker issue for
On Thu, Dec 17, 2015 at 11:05 AM, Derek Yarnell wrote:
> On 12/17/15 1:09 PM, Yehuda Sadeh-Weinraub wrote:
>>> Bug? Design?
>>
>> Somewhat a bug. The whole subusers that use s3 was unintentional, so
>> when creating the subuser api, we didn't think of needing the access
>>
On 12/17/15 3:15 PM, Yehuda Sadeh-Weinraub wrote:
>
> Right. Reading the code again:
>
> Try:
> GET /admin/metadata/user=cephtest
Thanks this is very helpful and works and I was able to also get the PUT
working. Only question is that is it expected to return a 204 no content?
2015-12-17
On Thu, Dec 17, 2015 at 2:44 PM, Derek Yarnell wrote:
> On 12/17/15 3:15 PM, Yehuda Sadeh-Weinraub wrote:
>>
>> Right. Reading the code again:
>>
>> Try:
>> GET /admin/metadata/user=cephtest
>
> Thanks this is very helpful and works and I was able to also get the PUT
>