-
Notifications
You must be signed in to change notification settings - Fork 6.6k
storage: bucket policy only samples #1976
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
Conversation
@@ -1,2 +1,3 @@ | |||
google-cloud-pubsub==0.38.0 | |||
google-cloud-storage==1.13.2 | |||
#google-cloud-storage==1.13.2 | |||
../google-cloud-python/storage |
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.
Need to have a valid requirements.txt and then pass Kokoro presubmit tests.
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.
Sg, should the review wait til then?
Clarifying context: The client is not yet released. I ran tests locally and they passed.
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.
Yes, I think samples here should only use released libraries so anybody could work from them. So this can just wait for that. Is that okay?
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.
Once the updated library is available, requirements.txt reflects that, and tests pass, this all looks good to me.
Hi,
Samples for the GCS Bucket Policy Only feature. The client library is not yet released to the Python package manager and requires a requirements.txt update before merge.