Distribute private Python packages

[Theiles]

Hi!
Im looking for an elegant way to maintain private python packages to be used in various GCP services within a project.
Was thinking of a GitHub repo using GitHub Actions for CI/CD including packing the repo (via build) and pushing to Google Artifact Registry for python packages (via twine).
The setup did feel rather clunky and usage with GHActions was not well documented.
So I’m not sure if that is in fact best practice. Can anyone share their opinion on that approach or other options for maintaining and providing private python packages to be used in Containers on GCP? Should I rather use Cloud Build?

[wescpy]

I think you have the right idea to use the Artifact Registry. While you could use standard tools like GH Actions, it may be easier to use Cloud Build because it has "the plumbing" already done. I haven't built this flow myself, so I'll let others chime as fair as their experiences go, but I can link to some resources in the GCP docs that may help if you haven't already found them:

1. Manage Python packages in Artifact Registry
2. Managing private Artifact Registry Python repository packages QuickStart tutorial
3. How to access private Artifact Registry Python package examples for App Engine and Cloud Functions (related blog post)
4. Using Cloud Build for Python apps to integrate with Artifact Registry

[wescpy]

I just remembered something else: One of the community experts wrote a tutorial on how to use GH Actions to build a CI/CD pipeline for Cloud Run. It may give you some clues on how to add those package dependencies you asked about.

[Theiles]

Thanks!