egister gcp-demo-multi --type gcp --auto-configureExample Command Output

```text

Successfully registered service connector `gcp-demo-multi` 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                             ┃

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

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

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

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

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

```

**NOTE**: from this point forward, we don't need the local GCP CLI credentials or the local GCP CLI at all. The steps that follow can be run on any machine regardless of whether it has been configured and authorized to access the GCP project.

4. find out which GCS buckets, GCR registries, and GKE Kubernetes clusters we can gain access to. We'll use this information to configure the Stack Components in our minimal GCP stack: a GCS Artifact Store, a Kubernetes Orchestrator, and a GCP Container Registry.

```sh

zenml service-connector list-resources --resource-type gcs-bucket

```

Example Command Output

```text

The following 'gcs-bucket' resources can be accessed by service connectors configured in your workspace: