2.9.12

Known issues

The annotations feature introduced in this release has an issue where project, flow_name or user annotations are not being populated for Kubernetes. This has been reverted in the next release.

Features

Custom annotations for K8S and Argo Workflows

This release enables users to add custom annotations to the Kubernetes resources that Flows create. The annotations can be configured much in the same way as custom labels

1. Globally with an environment variable. For example with

export METAFLOW_KUBERNETES_ANNOTATIONS="first=A,second=B"

2. At a step level by passing a dictionary to the Kubernetes decorator.

@kubernetes(annotations={"first": "A", "second": "B"})

What's Changed

• Adds custom annotations via env variables by @tylerpotts in #1442
• Pass the user-defined executable to environment's executable by @romain-intel in #1454
• Remove validate_environment from task lifecycle by @savingoyal in #1507
• Fix/863 - Improve error message in metaflow.S3 class when DATATOOLS_S3ROOT is not configured. by @tfurmston in #1491
• Fix an issue where 0 was not considered False for extension debug opt… by @romain-intel in #1511
• Bump version to 2.9.12 by @saikonen in #1514

Full Changelog: 2.9.11...2.9.12