Nope, you are right. I think it was just boto catching this for me and I took
that for granted.
I think that is the behavior I would expect too, S3-compliant restrictions on
create and allow legacy buckets to remain. Anyway, noticed you created a ticket
[0] in the tracker for this, thanks!
Be
On Tue, Oct 02, 2018 at 12:37:02PM -0400, Ryan Leimenstoll wrote:
> I was hoping to get some clarification on what "rgw relaxed s3 bucket
> names = false” is intended to filter.
Yes, it SHOULD have caught this case, but does not.
Are you sure it rejects the uppercase? My test also showed that it
Hi all,
I was hoping to get some clarification on what "rgw relaxed s3 bucket names =
false” is intended to filter. In our cluster (Luminous 12.2.8, serving S3) it
seems that RGW, with that setting set to false, is still allowing buckets with
underscores in the name to be created, although thi
