-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
#825: Allow passing explicit connection to 'Bucket.{list_blobs,make public}' #856
#825: Allow passing explicit connection to 'Bucket.{list_blobs,make public}' #856
Conversation
Ping me on this when we resolve #853 |
Rebased against updated branch for #853. |
Changes Unknown when pulling 1612c84 on tseaver:825-storage_bucket_list_blobs_make_public-explicit_connection into * on GoogleCloudPlatform:master*. |
Rebased again against updated branch for #853. |
@dhermes any remaining issues? |
Ditto here, was waiting on diffbase. |
OIC, you'd like a rebase against master. |
def __init__(self, bucket, extra_params=None): | ||
def __init__(self, bucket, extra_params=None, connection=None): | ||
if connection is None: | ||
connection = bucket.connection |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Ideally, the backend would have a special-purpose ACL for blobs where they "inherit"/"acquire" the permissions from their bucket; one could then leave them in that state as they were created, and toggle them all public / private just by manipulating the bucket's ACL. |
Unfortunately that ideal doesn't exist. |
LGTM |
…ke_public-explicit_connection #825: Allow passing explicit connection to 'Bucket.{list_blobs,make public}'
Requires #853.
See #825.