-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS::S3->add_bucket location param is undocumented and buggy #9
Comments
Version 0.14 on its way to CPAN shortly. Thanks! |
Actually, I don't think this fixed it. You can't pass "us-east-1" as a location constraint to S3. It responds with "The specified location-constraint is not valid". I think you can pass any other location though. This is dumb, but that's how S3 defines it. |
Gah! Thanks for the report, will fix. |
Actually, that may not be right. I'll explore further. |
Let me know, I've got a version here ready to upload that passes an empty string as the default rather than |
You can't pass "us-east-1" as a location constraint to S3. It responds with "The specified location-constraint is not valid". I think you can pass any other location though. This is dumb, but that's how S3 defines it. w/r/t 454bb7a
You can't pass "us-east-1" as a location constraint to S3. It responds with "The specified location-constraint is not valid". I think you can pass any other location though. This is dumb, but that's how S3 defines it. w/r/t 454bb7a
I did some live testing. My PR fixes the issue. |
Closing - as per #10 |
This parameter is not documented. While it shouldn't be required, it's passed to the request whether it was specified or not. So if I don't specify it then it ends up being passed as an
undef
and failing the TC for theAWS::S3::Request::CreateBucket
location
attribute.The text was updated successfully, but these errors were encountered: