👋 Hey folks! The most recent Orion release just shipped 🚀! On the heels of the recent rename of

Executor

to

TaskRunner

🏃, this release introduces

FlowRunner

🏃‍♂️, an analogous concept that specifies the infrastructure that a flow runs on. Just as a task runner can be specified for a flow, which encapsulates tasks, a flow runner can be specified for a deployment, which encapsulates a flow. This release includes two flow runners, which we expect to be the most commonly used: • SubprocessFlowRunner - The subprocess flow runner is the default flow runner. It allows for specification of a runtime Python environment with

virtualenv

and

conda

support. • DockerFlowRunner - Executes the flow run in a Docker container. The image, volumes, labels, and networks can be customized. From this release on, Docker images for use with this flow runner will be published with each release. Future releases will introduce runners for executing flows on Kubernetes and major cloud platform's container compute services (e.g. AWS ECS, Google Cloud Run). To learn more about flow runners and their relationship to deployments, check out their respective concepts docs themoreyouknow!