Repository navigation
ci(release): migrate google-vizier-dev PyPI publishing to OSS Exit Gate - #1339
Open
alonsopf89 wants to merge 1 commit into
Open
alonsopf89 wants to merge 1 commit into
alonsopf89 wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or 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
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.
Summary
Migrates
.github/workflows/pypi-publish-dev.ymlPyPI publishing (google-vizier-dev) to Google OSS Exit Gate (vizier/pypi) via keyless Workload Identity Federation (OIDC):google-github-actions/authandgoogle-github-actions/setup-gcloud(no static PyPI secrets).gcloud artifacts versions delete).https://us-python.pkg.dev/oss-exit-gate-prod/vizier--pypi/viatwineand uploads the release manifest togs://oss-exit-gate-prod-projects-bucket/vizier/pypi/manifests/.pypi-publish.ymlfor stablegoogle-vizierreleases is intentionally untouched in this PR; we can authorizepypi-publish.ymlin the Step 10 ownership handoff CL and migrate it in a follow-up PR once confirmed.)One-time PyPI Trusted Publisher setup (before next release)
Add
vizier-py@oss-exit-gate-prod.iam.gserviceaccount.comas a Google Cloud Trusted Publisher on PyPI (https://pypi.org/manage/project/google-vizier-dev/settings/publishing/).Verification
http://cl/1024944855) is submitted in#headand staging resources are provisioned.publish_all: false) passed againstvizier--pypiand staged test artifacts were cleaned up.Internal Reference (for Google maintainers):
http://go/oss-exit-gate(internal togoogle3; there is no public repo undergithub.com/google)http://b/576673325(Parent Epic:http://b/576673325)http://cl/1024944855