The Metaflow 2.2.6 release is a minor patch release.
- [Features](2.2.6_features)
- [Support AWS Fargate as compute backend for Metaflow tasks launched on AWS Batch](398)
- [Support `shared_memory`, `max_swap`, `swappiness` attributes for Metaflow tasks launched on AWS Batch](407)
- [Support wider very-wide workflows on top of AWS Step Functions](403)
- [Bug Fixes](2.2.6_bugs)
- [Assign tags to `Run` objects generated through AWS Step Functions executions](384)
- [Pipe all workflow set-up logs to `stderr`](378)
- [Handle null assignment to `IncludeFile` properly](418)
<a name="v2.2.6_features"></a> Features
[Support AWS Fargate as compute backend for Metaflow tasks launched on AWS Batch](398)
At [AWS re:invent 2020, AWS announced support for AWS Fargate](https://aws.amazon.com/blogs/aws/new-fully-serverless-batch-computing-with-aws-batch-support-for-aws-fargate/) as a compute backend (in addition to EC2) for AWS Batch. With this feature, Metaflow users can now submit their Metaflow jobs to AWS Batch Job Queues which are connected to AWS Fargate Compute Environments as well. By setting the environment variable - `METAFLOW_ECS_FARGATE_EXECUTION_ROLE `, users can configure the ecsTaskExecutionRole for the AWS Batch container and AWS Fargate agent. PR: #402
[Support `shared_memory`, `max_swap`, `swappiness` attributes for Metaflow tasks launched on AWS Batch](407)
The `batch` decorator now supports `shared_memory`, `max_swap`, `swappiness` attributes for Metaflow tasks launched on AWS Batch to provide a greater degree of control for memory management. PR: 408
[Support wider very-wide workflows on top of AWS Step Functions](403)
The tag `metaflow_version:` and `runtime:` is now available for all packaged executions and remote executions as well. This ensures that every run logged by Metaflow will have `metaflow_version` and `runtime` system tags available. PR: 403
<a name="v2.2.6_bugs"></a> Bug Fixes
[Assign tags to `Run` objects generated through AWS Step Functions executions](384)
`Run` objects generated by flows executed on top of AWS Step Functions were missing the tags assigned to the flow; even though the tags were correctly persisted to tasks. This release fixes and brings inline the tagging behavior as observed with local flow executions. PR: 386
[Pipe all workflow set-up logs to `stderr`](378)
Execution set-up logs for `conda` and `IncludeFile` were being piped to `stdout` which made manipulating the output of commands like `python flow.py step-functions create --only-json` a bit difficult. This release moves the workflow set-up logs to `stderr`. PR: 379
[Handle null assignment to `IncludeFile` properly](418)
A workflow executed without a required `IncludeFile` parameter would fail when the parameter was referenced inside the flow. This release fixes the issue by assigning a null value to the parameter in such cases. PR: 421