a Validator is such an example.

Related concepts:the Artifact Store is a type of Stack Component that needs to be registered as part of your ZenML Stack.

the objects circulated through your pipelines are serialized and stored in the Artifact Store using Materializers. Materializers implement the logic required to serialize and deserialize the artifact contents and to store them and retrieve their contents to/from the Artifact Store.

When to use it

The Artifact Store is a mandatory component in the ZenML stack. It is used to store all artifacts produced by pipeline runs, and you are required to configure it in all of your stacks.

Artifact Store Flavors

Out of the box, ZenML comes with a local artifact store already part of the default stack that stores artifacts on your local filesystem. Additional Artifact Stores are provided by integrations:

Artifact Store Flavor Integration URI Schema(s) Notes Local local built-in None This is the default Artifact Store. It stores artifacts on your local filesystem. Should be used only for running ZenML locally. Amazon S3 s3 s3 s3:// Uses AWS S3 as an object store backend Google Cloud Storage gcp gcp gs:// Uses Google Cloud Storage as an object store backend Azure azure azure abfs:// , az:// Uses Azure Blob Storage as an object store backend Custom Implementation custom custom Extend the Artifact Store abstraction and provide your own implementation

If you would like to see the available flavors of Artifact Stores, you can use the command:

zenml artifact-store flavor list

Every Artifact Store has a path attribute that must be configured when it is registered with ZenML. This is a URI pointing to the root path where all objects are stored in the Artifact Store. It must use a URI schema that is supported by the Artifact Store flavor. For example, the S3 Artifact Store will need a URI that contains the s3:// schema:

zenml artifact-store register s3_store -f s3 --path s3://my_bucket

How to use it