kip scoping its Resource Type during registration.a multi-instance Service Connector instance can be configured once and used to gain access to multiple resources of the same type, each identifiable by a Resource Name. Not all types of connectors and not all types of resources support multiple instances. Some Service Connectors Types like the generic Kubernetes and Docker connector types only allow single-instance configurations: a Service Connector instance can only be used to access a single Kubernetes cluster and a single Docker registry. To configure a multi-instance Service Connector, you can simply skip scoping its Resource Name during registration.

The following is an example of configuring a multi-type AWS Service Connector instance capable of accessing multiple AWS resources of different types:

zenml service-connector register aws-multi-type --type aws --auto-configure

Example Command Output

⠋ Registering service connector 'aws-multi-type'...

Successfully registered service connector `aws-multi-type` with access to the following resources:

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

┃     RESOURCE TYPE     │ RESOURCE NAMES                               ┃

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

┃    🔶 aws-generic     │ us-east-1                                    ┃

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

┃     📦 s3-bucket      │ s3://aws-ia-mwaa-715803424590                ┃

┃                       │ s3://zenfiles                                ┃

┃                       │ s3://zenml-demos                             ┃

┃                       │ s3://zenml-generative-chat                   ┃

┃                       │ s3://zenml-public-datasets                   ┃

┃                       │ s3://zenml-public-swagger-spec               ┃

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

┃ 🌀 kubernetes-cluster │ zenhacks-cluster                             ┃