Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Firebase Functions Python build cannot reliably install private Artifact Registry packages

Abierto
  • ¿Algo no está bien?
#271 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
google-cloud, python
Área
build-system, cloud

Línea de trabajo

Comienza revisando el buildpack google.python.pip indicado y el comando python3 -m pip install --requirement requirements.txt en la imagen de builder especificada. Reproduce el fallo con el requirements.txt de ejemplo y verifica los permisos de la cuenta de servicio de Cloud Build. Se considera terminado cuando un despliegue de Firebase Functions puede instalar el paquete privado de Artifact Registry sin vendorizarlo, usar pipelines personalizados ni recurrir a la contenerización.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature-request

Summary

Deploying Firebase Functions written in Python cannot reliably install private Python packages hosted in Google Artifact Registry using the documented authentication mechanism.

Although Artifact Registry supports authentication via the keyrings.google-artifactregistry-auth backend, the Firebase Functions build process installs dependencies in a single pip invocation. This creates a bootstrapping problem where the authentication backend must already be installed before pip attempts to resolve private dependencies.

As a result, private packages cannot be consumed out-of-the-box during function deployment causing deployment issues and ultimately meaning private packages cannot be consumed in firebase functions. Private Python packages are a common pattern for shared internal libraries, and the current limitation makes this workflow difficult.

Expected Behaviour

A Firebase Functions deployment should be able to install private Python packages hosted in Artifact Registry without requiring custom build pipelines, vendored wheels, or containerization.

For example, the following requirements.txt should work:

--extra-index-url https://<LOCATION>-python.pkg.dev/<PROJECT>/<REPO>/simple/

private-package==0.0.1

provided that:

  • the Cloud Build service account has artifactregistry.reader
  • the repository contains the package

Actual Behaviour

The Artifact Registry authentication mechanism requires the keyring backend to be present before pip attempts to fetch packages.

However pip resolves and downloads packages before installing their dependencies, meaning that adding the backend as a dependency does not help.

Example attempt:

--extra-index-url https://<LOCATION>-python.pkg.dev/<PROJECT>/<REPO>/simple/

keyring
keyrings.google-artifactregistry-auth
private-package==0.0.1

This still fails because pip attempts to resolve private-package before installing the keyring backend. This creates a bootstrap race condition

Why this is a Problem

The current behavior makes it effectively impossible to use private Artifact Registry Python packages with Firebase Functions without workarounds such as:

  • vendoring wheels into the repository
  • migrating to cloud run where the build process can be controlled

Environment Details

Builder image:

europe-west2-docker.pkg.dev/serverless-runtimes/google-22-full/builder/python:python_20260224_RC00_lightweight

Buildpacks used:

google.utils.archive-source
google.python.runtime
google.python.functions-framework
google.python.pip
google.utils.label-image
google.python.link-runtime

The pip step is executed as:

python3 -m pip install --requirement requirements.txt

Python runtime:

Python 3.13.12

Suggested Solutions

Option 1: Preinstall Artifact Registry authentication backend

Ensure the build environment includes:

keyring
keyrings.google-artifactregistry-auth

before the pip install step.

Option 2: Two-phase dependency install

Modify the Python buildpack to run:

pip install keyring keyrings.google-artifactregistry-auth
pip install -r requirements.txt
Lenguaje dominante
Python
Estrellas
167
Forks
36
Merge medio
4 d 3 h
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de firebase/firebase-functions-python

Todos los issues de firebase/firebase-functions-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.