registry │ demozenmlcontainerregistry.azurecr.io ┃┗━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

zenml service-connector login azure-service-principal --resource-type docker-registry --resource-id demozenmlcontainerregistry.azurecr.io

Example Command Output

⠹ Attempting to configure local client using service connector 'azure-service-principal'...

WARNING! Your password will be stored unencrypted in /home/stefan/.docker/config.json.

Configure a credential helper to remove this warning. See

https://docs.docker.com/engine/reference/commandline/login/#credentials-store

The 'azure-service-principal' Docker Service Connector connector was used to successfully configure the local Docker/OCI container registry client/SDK.

The local Docker CLI can now be used to interact with the container registry:

docker push demozenmlcontainerregistry.azurecr.io/zenml:example_pipeline

Example Command Output

The push refers to repository [demozenmlcontainerregistry.azurecr.io/zenml]

d4aef4f5ed86: Pushed

2d69a4ce1784: Pushed

204066eca765: Pushed

2da74ab7b0c1: Pushed

75c35abda1d1: Layer already exists

415ff8f0f676: Layer already exists

c14cb5b1ec91: Layer already exists

a1d005f5264e: Layer already exists

3a3fd880aca3: Layer already exists

149a9c50e18e: Layer already exists

1f6d3424b922: Layer already exists

8402c959ae6f: Layer already exists

419599cb5288: Layer already exists

8553b91047da: Layer already exists

connectors: digest: sha256:a4cfb18a5cef5b2201759a42dd9fe8eb2f833b788e9d8a6ebde194765b42fe46 size: 3256

It is also possible to update the local Azure CLI configuration with credentials extracted from the Azure Service Connector:

zenml service-connector login azure-service-principal --resource-type azure-generic

Example Command Output

Updated the local Azure CLI configuration with the connector's service principal credentials.

The 'azure-service-principal' Azure Service Connector connector was used to successfully configure the local Generic Azure resource client/SDK.