Skip to content

In this tutorial, we will register a package in GCP Artifact Registry both manually as well as with CICD. In the end, you will be able to install your own private package with pip just like you're used to.

Notifications You must be signed in to change notification settings

godatadriven/private-package-in-gcp-tutorial

Repository files navigation

How to register and install your own private Python package in GCP Artifact Registry

In the following tutorial, we will register and install a private Python package in GCP Artifact Registry. We will do this in two ways: manually and with CICD (Github Actions). In the end, you will be able to install your own private Python package in your Python projects, by adding it to your requirements as you're used to!

For more info, see the official documentation. See this documentation page for more info about authentication with GCP Artifact Registry. See this blog post for more info on how to package your Python code.

Register and install package manually

  1. Create a repository in GCP Artifact Registry to store our package:

    1. Navigate to Artifact Registry
    2. Click + CREATE REPOSITORY
    3. Give it an appropriate name
    4. Select Format: Python
    5. Pick a region near you
  2. Make sure you're logged in with the gcloud CLI:

gcloud auth login
  1. Create a virtual environment and activate it
python -m venv .venv
source .venv/bin/activate
  1. Copy and rename env.template to .env and set variables:
PROJECT_ID=<your-project-id>
REPOSITORY=<your-artifact-registry-repository-name>
LOCATION=<the-location-of-your-repository>
  1. Make environment variables available to your shell.
set -a  # configure variable assignments to be exported
source .env  # set the variables
  1. Install the following libraries:
pip install build  # for building our package
pip install twine  # for uploading the package to GCP Artifact Registry
pip install keyring  # for storing credentials
pip install keyrings.google-artifactregistry-auth  # for storing credentials
  1. Create a .pypirc file in your home directory. Note: this overwrites an existing .pypirc file if it exists. If you have an existing .pypirc file, you should manually add the following profile to it.
echo "[distutils]
index-servers =
    ${REPOSITORY}

[${REPOSITORY}]
repository: https://${LOCATION}-python.pkg.dev/${PROJECT_ID}/${REPOSITORY}/" > ~/.pypirc
  1. Create a pip.conf file in your virtual environment:
echo "[global]
extra-index-url = https://${LOCATION}-python.pkg.dev/${PROJECT_ID}/${REPOSITORY}/simple/" > .venv/pip.conf
  1. Build your package. This will create a dist directory with a .tar.gz and .whl file in it.
python -m build
  1. Upload your package to GCP Artifact Registry:
python -m twine upload -r ${REPOSITORY} dist/*
  1. Install your package from GCP Artifact Registry:
pip install your-own-private-package

Register package with CICD (Github Actions)

  1. Fork this Github repository, so you will be able to add secrets to it later on. You can also use your own repository, but you will need to update the CICD configuration accordingly.
  2. Navigate to IAM & Admin > Service Accounts in GCP
  3. Create a new service account with the "Artifact Registry Writer" role
  4. Add a key to the service account and download it as a JSON file. Never commit this file to your repository!
  5. Add the following secrets to your Github repository, under Settings > Secrets and variables > Actions > Repository secrets:
    • PROJECT_ID: your GCP project ID
    • LOCATION: the location of your Artifact Registry repository
    • REPOSITORY: the name of your Artifact Registry repository
    • SA_KEY_BASE64: the contents of the service account JSON file you downloaded in step 3, base64 encoded. You can use the following command to base64 encode the file:
base64 -i <path-to-json-file>
  1. There are two ways to trigger the provided workflow in .github/workflows/register-package.yaml:
    1. Manually, by clicking Run workflow in the Actions tab of your Github repository
    2. Automatically, by pushing a new tag to your repository. The tag name must start with v and be followed by a version number, e.g. v1.0.0. You can do this by running the following command:
git tag v1.0.0
git push origin v1.0.0
  1. Check the Actions tab in your Github repository to see the CICD pipeline in action. You can also check the Artifact Registry repository to see if your package was uploaded successfully.

Wrap up

Congratulations! You have successfully registered and installed your own private Python package in GCP Artifact Registry. Provided you set up your pip index as outlined in the first section, you can now use this package in your Python projects, by adding it to your requirements as you're used to! 🎉

About

In this tutorial, we will register a package in GCP Artifact Registry both manually as well as with CICD. In the end, you will be able to install your own private package with pip just like you're used to.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages