─────────────────────────────────────────────────┨┃ UPDATED_AT       │ 2023-05-19 08:09:44.102936                                               ┃

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

Configuration

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

┃ PROPERTY          │ VALUE      ┃

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

┃ project_id        │ zenml-core ┃

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

┃ user_account_json │ [HIDDEN]   ┃

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

GCP Service Account

Long-lived GCP credentials consisting of a GCP service account and its credentials.

This method requires a GCP service account and a service account key JSON created for it.

By default, the GCP connector generates temporary OAuth 2.0 tokens from the service account credentials and distributes them to clients. The tokens have a limited lifetime of 1 hour. This behavior can be disabled by setting the generate_temporary_tokens configuration option to False, in which case, the connector will distribute the service account credentials JSON to clients instead (not recommended).

A GCP project is required and the connector may only be used to access GCP resources in the specified project.

If you already have the GOOGLE_APPLICATION_CREDENTIALS environment variable configured to point to a service account key JSON file, it will be automatically picked up when auto-configuration is used.

The following assumes a GCP service account was created, granted permissions to access GCS buckets in the target project and a service account key JSON was generated and saved locally in the connectors-devel@zenml-core.json file:

zenml service-connector register gcp-service-account --type gcp --auth-method service-account --resource-type gcs-bucket --project_id=zenml-core --service_account_json=@connectors-devel@zenml-core.json

Example Command Output

Expanding argument value service_account_json to contents of file connectors-devel@zenml-core.json.