N -x mlflow_bucket=gs://my_bucket

Artifact StoresFor an artifact store, you can pass bucket_name as an argument to the command.

zenml artifact-store deploy s3_artifact_store --flavor=s3 --provider=aws -r YOUR_REGION -x bucket_name=my_bucket

Container Registries

For container registries, you can pass the repository name using repo_name:

zenml container-registry deploy aws_registry --flavor=aws -p aws -r YOUR_REGION -x repo_name=my_repo

This is only useful for the AWS case since AWS requires a repository to be created before pushing images to it and the deploy command ensures that a repository with the name you provide is created. In case of GCP and other providers, you can choose the repository name at the same time as you are pushing the image via code. This is achieved through setting the target_repo attribute of the DockerSettings object.

Other configuration

In the case of GCP components, it is required that you pass a project ID to the command as extra configuration when you're creating any GCP resource.

PreviousManage stacks

NextDeploy a stack using mlstacks

Last updated 15 days ago