Skip to content
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 'Blob.{rename,delete}'. #854

Merged
merged 1 commit into from
May 4, 2015
Merged

#825: Allow passing explicit connection to 'Blob.{rename,delete}'. #854

merged 1 commit into from
May 4, 2015

Conversation

tseaver
Copy link
Contributor

@tseaver tseaver commented May 1, 2015

See #825.

Needs #843 as a base ('Bucket.copy_blob' and 'Bucket.delete_blob' must also take optional 'connection').

@tseaver tseaver added the api: storage Issues related to the Cloud Storage API. label May 1, 2015
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label May 1, 2015
@tseaver
Copy link
Contributor Author

tseaver commented May 1, 2015

Rebased after merge of #843.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fc9b6d6 on tseaver:825-storage_blob-explicit_connection into * on GoogleCloudPlatform:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling f4f51cf on tseaver:825-storage_blob-explicit_connection into * on GoogleCloudPlatform:master*.

@dhermes
Copy link
Contributor

dhermes commented May 4, 2015

LGTM

tseaver added a commit that referenced this pull request May 4, 2015
…tion

#825: Allow passing explicit connection to 'Blob.{rename,delete}'.
@tseaver tseaver merged commit 2e629e0 into googleapis:master May 4, 2015
@tseaver tseaver deleted the 825-storage_blob-explicit_connection branch July 22, 2015 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API. cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants