Skip to content
This repository was archived by the owner on Mar 31, 2026. It is now read-only.

fix: changeover unspecified to inherited - #603

Merged
unforced merged 11 commits into
googleapis:mainfrom
unforced:pap_change
Sep 29, 2021
Merged

fix: changeover unspecified to inherited#603
unforced merged 11 commits into
googleapis:mainfrom
unforced:pap_change

Conversation

@unforced

Copy link
Copy Markdown
Contributor

Fixes#597 🦕

@unforced
unforced requested review from a team, cojenco and shaffeeullahSeptember 28, 2021 17:42
@product-auto-labelproduct-auto-labelBot added the api: storage Issues related to the googleapis/python-storage API. label Sep 28, 2021
@google-clagoogle-claBot added the cla: yes This human has signed the Contributor License Agreement. label Sep 28, 2021
Comment threadgoogle/cloud/storage/constants.py
Comment threadgoogle/cloud/storage/constants.py
Comment threadgoogle/cloud/storage/bucket.py
Comment threadgoogle/cloud/storage/bucket.py Outdated
Comment threadtests/unit/test_bucket.py Outdated
Co-authored-by: Tres Seaver <tseaver@palladion.com>
@google-cla

Copy link
Copy Markdown

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
Copy Markdown

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-clagoogle-claBot 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
Copy Markdown

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
Copy Markdown

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
Copy Markdown
ContributorAuthor

@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
Copy Markdown
Contributor

@googlebot I consent.

@google-cla

Copy link
Copy Markdown

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
Copy Markdown
Contributor

@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.

@unforcedunforced 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
Copy Markdown

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-clagoogle-claBot 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
@unforcedunforced 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-clagoogle-claBot 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
@cojencocojenco 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
Copy Markdown

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-clagoogle-claBot 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
@unforcedunforced 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 reviewSeptember 29, 2021 00:55

All changes resolved, and approval was given.

@unforced

Copy link
Copy Markdown
ContributorAuthor

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
Copy Markdown
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
Copy Markdown
ContributorAuthor

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
Copy Markdown

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-clagoogle-claBot 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
Copy Markdown
Contributor

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

@unforcedunforced 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-kokoroyoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 29, 2021
@unforcedunforced added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 29, 2021
@yoshi-kokoroyoshi-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:mainSep 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>
@release-pleaserelease-pleaseBot mentioned this pull request Jan 12, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: storageIssues related to the googleapis/python-storage API.cla: yesThis 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

@unforced@tseaver@cojenco@yoshi-kokoro