ucket         │ user-account    │       │        ┃┃                       │        │ 🌀 kubernetes-cluster │ service-account │       │        ┃

┃                       │        │ 🐳 docker-registry    │ oauth2-token    │       │        ┃

┃                       │        │                       │ impersonation   │       │        ┃

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

```

Register an individual single-instance GCP Service Connector using auto-configuration for each of the resources that will be needed for the Stack Components: a GCS bucket, a GCR registry, and generic GCP access for the VertexAI orchestrator and another one for the GCP Cloud Builder:Copyzenml service-connector register gcs-zenml-bucket-sl --type gcp --resource-type gcs-bucket --resource-id gs://zenml-bucket-sl --auto-configure

Example Command Output

```text

Successfully registered service connector `gcs-zenml-bucket-sl` with access to the following resources:

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

┃ RESOURCE TYPE │ RESOURCE NAMES       ┃

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

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

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

```

```sh

zenml service-connector register gcr-zenml-core --type gcp --resource-type docker-registry --auto-configure

```

Example Command Output

```text

Successfully registered service connector `gcr-zenml-core` with access to the following resources:

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

┃   RESOURCE TYPE    │ RESOURCE NAMES    ┃

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

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

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

```

```sh

zenml service-connector register vertex-ai-zenml-core --type gcp --resource-type gcp-generic --auto-configure

```

Example Command Output

```text

Successfully registered service connector `vertex-ai-zenml-core` with access to the following resources:

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

┃ RESOURCE TYPE  │ RESOURCE NAMES ┃