keyrings.google-artifactregistry-auth fails to install backend on runtimes > 10.4

Ryan512 — Thu, 11 Apr 2024 19:02:36 GMT

We run Databricks on GCP. We store our private Python packages in the Google Artifact Registry. When we need to install the private packages we a global init script to install `keyring` and `keyrings.google-artifactregistry-auth`. The we `pip install -extra-index-url <our index URL> our_packages` either from cluster init scripts or a cell in a notebook. The clusters have Google Service Accounts that have access to the Artifact Registry. When we do this with a Databricks runtime of 10.4ML or less, everything works as expected, and our dependencies are installed correctly.

When we do this procedure with any runtime greater than 10.4, it fails. Specifically the `keyrings.google-artifactregistry-auth` does not or is unable to set up the need backend with `keyring`. When we run the command

```

%sh

keyring --list-backends

```

It does not list `GooglePythonAuth` as one of the backends. I can run `%pip freeze` and verify that `keyring` and `keyrings.google-artifactregistry-auth` are installed by pip. I can run `%pip install keyrings.google-artifactregistry-auth` in a notebook successfully too, but the `GooglePythonAuth` keyring is never setup. This only happens on runtimes greater than 10.4.

How can get the keyring to install or setup on later versions?

Re: keyrings.google-artifactregistry-auth fails to install backend on runtimes > 10.4

Heberg — Mon, 06 May 2024 17:38:33 GMT

Hayyyyyyy

topic Re: keyrings.google-artifactregistry-auth fails to install backend on runtimes > 10.4 in Administration & Architecture

keyrings.google-artifactregistry-auth fails to install backend on runtimes > 10.4

Re: keyrings.google-artifactregistry-auth fails to install backend on runtimes > 10.4