━━━━━━┷━━━━━━━━┷━━━━━━━━━┛

Other stack componentsThere are many more components that you can add to your stacks, like experiment trackers, model deployers, and more. You can see all supported stack component types in a single table view here

Perhaps the most important stack component after the orchestrator and the artifact store is the container registry. A container registry stores all your containerized images, which hold all your code and the environment needed to execute them. We will learn more about them in the next section!

Registering a stack

Just to illustrate how to interact with stacks, let's create an alternate local stack. We start by first creating a local artifact store.

Create an artifact store

zenml artifact-store register my_artifact_store --flavor=local

Let's understand the individual parts of this command:

artifact-store : This describes the top-level group, to find other stack components simply run zenml --help

register : Here we want to register a new component, instead, we could also update , delete and more zenml artifact-store --help will give you all possibilities

my_artifact_store : This is the unique name that the stack component will have.

--flavor=local: A flavor is a possible implementation for a stack component. So in the case of an artifact store, this could be an s3-bucket or a local filesystem. You can find out all possibilities with zenml artifact-store flavor --list

This will be the output that you can expect from the command above.

Using the default local database.

Running with active workspace: 'default' (global)

Running with active stack: 'default' (global)

Successfully registered artifact_store `my_artifact_store`.bash

To see the new artifact store that you just registered, just run:

zenml artifact-store describe my_artifact_store

Create a local stack

With the artifact store created, we can now create a new stack with this artifact store.

zenml stack register a_new_local_stack -o default -a my_artifact_store