localstack with a cloud-based stack, which you can configure.
.zenfolder. There is not much configuration to it - it just works out of the box.
.zendirectory created when you run
zenml initat the very beginning. All artifacts and inputs will be persisted there.
rootof any pipeline job, that controls how and where each individual step within a pipeline is executed. Therefore, the orchestrator can be used to great effect to scale jobs in production.
OrchestratorGCPBackend. It spins up a VM on your GCP projects, zips up your local code to the instance, and executes the ZenML pipeline with a Docker Image of your choice.