Skip to content

ci: migrate PyPI publishing workflow to OSS Exit Gate - #1352

Open
alonsopf89 wants to merge 1 commit into
google:masterfrom
alonsopf89:oss-exit-gate-pypi
Open

alonsopf89 wants to merge 1 commit into
google:masterfrom
alonsopf89:oss-exit-gate-pypi

Conversation

@alonsopf89

Copy link
Copy Markdown

Migrates PyPI package publishing in .github/workflows/publish-python.yml to Google OSS Exit Gate (jsonnet/pypi) using Workload Identity Federation (OIDC) instead of direct PyPI credentials/tokens.

Summary of Changes

  • Authenticates to Google Cloud via google-github-actions/auth (OIDC Workload Identity Federation — zero long-lived secrets required).
  • Stages built distributions (dist/*) to the provisioned Artifact Registry repository (https://us-python.pkg.dev/oss-exit-gate-prod/jsonnet--pypi/).
  • Uploads a release manifest (manifest.json) to gs://oss-exit-gate-prod-projects-bucket/jsonnet/pypi/manifests/ to trigger OSS Exit Gate validation and downstream PyPI publication.
  • Pins GitHub Actions to full 40-character commit SHAs with least-privilege permissions (persist-credentials: false, contents: read).

Production OSS Exit Gate resources and end-to-end Artifact Registry + GCS Smoke Tests have already been verified.

Bug: b/579644704 (Parent: b/576673325)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant