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

fix: changeover unspecified to inherited #603

Merged
merged 11 commits into from Sep 29, 2021
Merged

Conversation

unforced
Copy link
Contributor

Fixes #597 🦕

@unforced unforced requested review from a team as code owners September 28, 2021 17:42
@product-auto-label product-auto-label bot added the api: storage Issues related to the googleapis/python-storage API. label Sep 28, 2021
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Sep 28, 2021
google/cloud/storage/constants.py Outdated Show resolved Hide resolved
google/cloud/storage/constants.py Outdated Show resolved Hide resolved
google/cloud/storage/bucket.py Show resolved Hide resolved
google/cloud/storage/bucket.py Outdated Show resolved Hide resolved
tests/unit/test_bucket.py Outdated Show resolved Hide resolved
Co-authored-by: Tres Seaver <tseaver@palladion.com>
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 28, 2021
Co-authored-by: Tres Seaver <tseaver@palladion.com>
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@unforced
Copy link
Contributor Author

@tseaver should I go back and change the commits so I write them rather than just including your suggestions? Or are you able to get the Google/Github CLA thing taken care of from your end?

@tseaver
Copy link
Contributor

tseaver commented Sep 28, 2021

@googlebot I consent.

@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@tseaver
Copy link
Contributor

tseaver commented Sep 28, 2021

@Breathtender As a Googler, you should be able to manually flip the label from cla: no to cla: yes. I don't know why, but the CLA bot sometimes loses its mind about merged suggestions.

@unforced unforced added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 28, 2021
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 28, 2021
@unforced unforced added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 28, 2021
@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 28, 2021
@cojenco cojenco added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 28, 2021
@google-cla
Copy link

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 28, 2021
@unforced unforced added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 29, 2021
@unforced unforced dismissed tseaver’s stale review September 29, 2021 00:55

All changes resolved, and approval was given.

@unforced
Copy link
Contributor Author

Ah, seems we still need a review, after navigating some strange lint issues.

Comment on lines 483 to 484
"""Setting for public access prevention policy. Options are 'inherited' (default) or 'enforced'.
See: https://cloud.google.com/storage/docs/public-access-prevention
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still needs the blank line to separate summary from body.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah strange, I think the blank line caught the linter, which is why I changed it back. But perhaps I had just left white space in the line which was the issue.

@google-cla
Copy link

google-cla bot commented Sep 29, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Sep 29, 2021
@tseaver
Copy link
Contributor

tseaver commented Sep 29, 2021

@Breathtender One more manual flip of the CLA flag, and you should be good to go.

@unforced unforced added cla: yes This human has signed the Contributor License Agreement. kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Sep 29, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 29, 2021
@unforced unforced added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 29, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 29, 2021
@unforced unforced merged commit 283a419 into googleapis:main Sep 29, 2021
cojenco added a commit to cojenco/python-storage that referenced this pull request Oct 13, 2021
* fix: changeover unspecified to inherited

* Update google/cloud/storage/bucket.py

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* Apply suggestions from code review

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* remove dup line

* Apply suggestions from code review

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* Update tests/unit/test_bucket.py

Co-authored-by: cojenco <cathyo@google.com>

* lint fix

* one more lint fix

* line

Co-authored-by: Tres Seaver <tseaver@palladion.com>
Co-authored-by: cojenco <cathyo@google.com>
cojenco added a commit to cojenco/python-storage that referenced this pull request Oct 13, 2021
* fix: changeover unspecified to inherited

* Update google/cloud/storage/bucket.py

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* Apply suggestions from code review

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* remove dup line

* Apply suggestions from code review

Co-authored-by: Tres Seaver <tseaver@palladion.com>

* Update tests/unit/test_bucket.py

Co-authored-by: cojenco <cathyo@google.com>

* lint fix

* one more lint fix

* line

Co-authored-by: Tres Seaver <tseaver@palladion.com>
Co-authored-by: cojenco <cathyo@google.com>
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 googleapis/python-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.

Change Public Access Prevention "unspecified" to "inherited"
4 participants