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.

Sign up for GitHub

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

Jump to bottom

API unmapped: storage.buckets.update #1430

Closed
tseaver opened this issue Jan 29, 2016 · 2 comments
Closed

API unmapped: storage.buckets.update #1430

tseaver opened this issue Jan 29, 2016 · 2 comments
Assignees
@tseaver
Labels
api: storage Issues related to the Cloud Storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@tseaver
Copy link
Contributor

tseaver commented Jan 29, 2016

Noted in #1420: https://github.com/GoogleCloudPlatform/gcloud-python/pull/1420/files#diff-50dad309c06e8edd83f86b8e40b32a85R287
@tseaver tseaver added the api: storage Issues related to the Cloud Storage API. label Jan 29, 2016
@tseaver tseaver mentioned this issue Jan 29, 2016
Closed
@dhermes
Copy link
Contributor

dhermes commented Jan 29, 2016

@tseaver The point of the comment is that we don't need to implement it since patch exists.

@lukesneeringer lukesneeringer added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Apr 19, 2017
@tseaver
Copy link
Contributor Author

tseaver commented Jul 26, 2017

The storageClass property can apparently be set via update but not patch, but we expose a custom API which does that now via a rewrite.

@tseaver tseaver closed this as completed Jul 26, 2017
@tseaver tseaver mentioned this issue Aug 1, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tseaver tseaver

Labels
api: storage Issues related to the Cloud Storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lukesneeringer @tseaver @dhermes