nes/cec118d1-d90a-44ec-8bd7-d978f726b7aa/runs

```This is an example of an end-to-end workflow involving Service Connectors that use multiple single-instance GCP Service Connectors, each giving access to a resource for a Stack Component. A complete ZenML Stack is registered and composed of the following Stack Components, all connected through its individual Service Connector:

a VertexAI Orchestrator connected to the GCP project

a GCS Artifact Store connected to a GCS bucket

a GCR Container Registry connected to a GCR container registry

a Google Cloud Image Builder connected to the GCP project

As a last step, a simple pipeline is run on the resulting Stack.

Configure the local GCP CLI with valid user account credentials with a wide range of permissions (i.e. by running gcloud auth application-default login) and install ZenML integration prerequisites:Copyzenml integration install -y gcpCopygcloud auth application-default login

Example Command Output

```text

Credentials saved to file: [/home/stefan/.config/gcloud/application_default_credentials.json]

These credentials will be used by any library that requests Application Default Credentials (ADC).

Quota project "zenml-core" was added to ADC which can be used by Google client libraries for billing

and quota. Note that some services may still bill the project owning the resource.

```

Make sure the GCP Service Connector Type is availableCopyzenml service-connector list-types --type gcp

Example Command Output

```text

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

┃         NAME          │ TYPE   │ RESOURCE TYPES        │ AUTH METHODS    │ LOCAL │ REMOTE ┃

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

┃ GCP Service Connector │ 🔵 gcp │ 🔵 gcp-generic        │ implicit        │ ✅    │ ✅     ┃

┃                       │        │ 📦 gcs-bucket         │ user-account    │       │        ┃