s3.Bucket can't be used for cross-account buckets #1063
Labels
feature-request
This issue requests a feature.
Comments
kmosher
added a commit
to kmosher/boto3
that referenced
this issue
Apr 15, 2017
This will cause it to no longer fail if creation_date can't be found via ListBuckets (boto#1063)
|
I think that plan sounds reasonable. Thanks for the pull request. |
dstufft
pushed a commit
that referenced
this issue
Apr 28, 2017
* Make s3.Bucket.load() more accepting of failure This will cause it to no longer fail if creation_date can't be found via ListBuckets (#1063) * Only swallow ListBuckets AccessDenied errors
kmosher
added a commit
to kmosher/botocore
that referenced
this issue
May 3, 2017
|
The PR has been merged. So closing the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The S3 API is weird in that you can't directly interrogate a bucket's creation date. The only place it appears is in ListBuckets output. So in #128 a custom loader was added for Bucket that reads through ListBuckets to grab this info.
The problem is, ListBuckets only contains buckets owned by your current account. If you try to instantiate a
Bucketwith the name of bucket from a second account, the loader will 404, even if you've been granted cross-account permissions on that bucket.I'd suggest that load() should opportunistically set the creation_date as is done now, but not fail if it can't be set. Then update the docs to not it will sometimes be None in cases where the bucket is owned by another account (or you lack ListBucket perms).
The text was updated successfully, but these errors were encountered: