issions that are granted to the connector clients.To find out more about Application Default Credentials, see the GCP ADC documentation.

A GCP project is required and the connector may only be used to access GCP resources in the specified project. When used remotely in a GCP workload, the configured project has to be the same as the project of the attached service account.

The following assumes the local GCP CLI has already been configured with user account credentials by running the gcloud auth application-default login command:

zenml service-connector register gcp-implicit --type gcp --auth-method implicit --auto-configure

Example Command Output

Successfully registered service connector `gcp-implicit` with access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓

┃     RESOURCE TYPE     │ RESOURCE NAMES                                  ┃

┠───────────────────────┼─────────────────────────────────────────────────┨

┃    🔵 gcp-generic     │ zenml-core                                      ┃

┠───────────────────────┼─────────────────────────────────────────────────┨

┃     📦 gcs-bucket     │ gs://zenml-bucket-sl                            ┃

┃                       │ gs://zenml-core.appspot.com                     ┃

┃                       │ gs://zenml-core_cloudbuild                      ┃

┃                       │ gs://zenml-datasets                             ┃

┃                       │ gs://zenml-internal-artifact-store              ┃

┃                       │ gs://zenml-kubeflow-artifact-store              ┃

┃                       │ gs://zenml-project-time-series-bucket           ┃

┠───────────────────────┼─────────────────────────────────────────────────┨

┃ 🌀 kubernetes-cluster │ zenml-test-cluster                              ┃

┠───────────────────────┼─────────────────────────────────────────────────┨

┃  🐳 docker-registry   │ gcr.io/zenml-core                               ┃