build: use PyPI API token in secret manager #1040
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
google-cla
bot
added
the
cla: yes
parthea
approved these changes
Apr 14, 2021
chingor13
reviewed
Apr 14, 2021
|
@chingor @parthea PTAL |
parthea
approved these changes
Apr 14, 2021
busunkim96
added
the
automerge
chingor13
approved these changes
Apr 14, 2021
gcf-merge-on-green
bot
removed
the
automerge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate python libraries onto the PyPI API token stored in secret manager.
A PyPI API token is limited in scope to uploading new releases. https://pypi.org/help/#apitoken
Verified that this works with build on googleapis/python-vision#136