━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━┷━━━━━━━┷━━━━━━━━┛A lot more is hidden behind a Service Connector Type than a name and a simple list of resource types. Before using a Service Connector Type to configure a Service Connector, you probably need to understand what it is, what it can offer and what are the supported authentication methods and their requirements. All this can be accessed directly through the CLI. Some examples are included here.

Showing information about the gcp Service Connector Type:

zenml service-connector describe-type gcp

Example Command Output

╔══════════════════════════════════════════════════════════════════════════════╗

║                🔵 GCP Service Connector (connector type: gcp)                ║

╚══════════════════════════════════════════════════════════════════════════════╝

Authentication methods:

🔒 implicit

🔒 user-account

🔒 service-account

🔒 oauth2-token

🔒 impersonation

Resource types:

🔵 gcp-generic

📦 gcs-bucket

🌀 kubernetes-cluster

🐳 docker-registry

Supports auto-configuration: True

Available locally: True

Available remotely: True

The ZenML GCP Service Connector facilitates the authentication and access to

managed GCP services and resources. These encompass a range of resources,

including GCS buckets, GCR container repositories and GKE clusters. The

connector provides support for various authentication methods, including GCP

user accounts, service accounts, short-lived OAuth 2.0 tokens and implicit

authentication.

To ensure heightened security measures, this connector always issues short-lived

OAuth 2.0 tokens to clients instead of long-lived credentials. Furthermore, it

includes automatic configuration and detection of  credentials locally

configured through the GCP CLI.

This connector serves as a general means of accessing any GCP service by issuing

OAuth 2.0 credential objects to clients. Additionally, the connector can handle

specialized authentication for GCS, Docker and Kubernetes Python clients. It