-
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
Storage: add 'Bucket.location_type' property. #8089
Storage: add 'Bucket.location_type' property. #8089
Conversation
See | ||
https://cloud.google.com/storage/docs/json_api/v1/buckets#storageClass | ||
https://cloud.google.com/storage/docs/storage-classes | ||
""" | ||
|
||
MULTI_REGION_LOCATION_TYPE = "MULTI_REGION" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"MULTI_REGION", "REGION", and" DUAL_REGION" were supposed to be "multi-region", "region", and "dual-region". This will be changed in the API after a rollout on June 26 and should also be reflected here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"MULTI_REGION", "REGION", and" DUAL_REGION" were supposed to be "multi-region", "region", and "dual-region". This will be changed in the API after a rollout on June 26 and should also be reflected here.
@JesseLovelace What about the other storage classes ( |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the ℹ️ Googlers: Go here for more info. |
Un-deprecate STANDARD storage class. Docs-deprecate storage classes implying location type.
Include named constants for allowed 'location_type' values.
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
@crwilcox I mistakenly rebased against |
ContainerAnalysis and Grafeas failures are due to a Kokoro-internal glitch. |
@JesseLovelace PTAL. |
@JesseLovelace I'm going to merge this PR into the @frankyn Please let me know when we are ready to merge that branch to master. |
- Add named constants for allowed 'storage_class' values. - Un-deprecate STANDARD storage class. - Docs-deprecate storage classes implying location type. - Add 'Bucket.location_type' property. - Add named constants for allowed 'location_type' values.
- Add named constants for allowed 'storage_class' values. - Un-deprecate STANDARD storage class. - Docs-deprecate storage classes implying location type. - Add 'Bucket.location_type' property. - Add named constants for allowed 'location_type' values.
"NEARLINE", | ||
"COLDLINE", | ||
"STANDARD", # alias for MULTI_REGIONAL/REGIONAL, based on location | ||
"DURABLE_REDUCED_AVAILABILITY", # deprecated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is renaming these a breaking change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There isn't any renaming happening, just naming: the existing code used string literals, while the PR adds named constants for them.
- Add named constants for allowed 'storage_class' values. - Un-deprecate STANDARD storage class. - Docs-deprecate storage classes implying location type. - Add 'Bucket.location_type' property. - Add named constants for allowed 'location_type' values.
No description provided.