gistry or even more than one type of GCP resource:zenml service-connector register --type gcp -i

A non-interactive CLI example that leverages the GCP CLI configuration on your local machine to auto-configure a GCP Service Connector targeting a GCR registry is:

zenml service-connector register <CONNECTOR_NAME> --type gcp --resource-type docker-registry --auto-configure

Example Command Output

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

⠸ Registering service connector 'gcp-zenml-core'...

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

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

┃   RESOURCE TYPE    │ RESOURCE NAMES    ┃

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

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

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

Note: Please remember to grant the entity associated with your GCP credentials permissions to read and write to your GCR registry. For a full list of permissions required to use a GCP Service Connector to access a GCR registry, please refer to the GCP Service Connector GCR registry resource type documentation or read the documentation available in the interactive CLI commands and dashboard. The GCP Service Connector supports many different authentication methods with different levels of security and convenience. You should pick the one that best fits your use-case.

If you already have one or more GCP Service Connectors configured in your ZenML deployment, you can check which of them can be used to access the GCR registry you want to use for your GCP Container Registry by running e.g.:

zenml service-connector list-resources --connector-type gcp --resource-type docker-registry

Example Command Output

The following 'docker-registry' resources can be accessed by 'gcp' service connectors configured in your workspace:

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