Hello team, a very small request: is it possible to extend the functionality of

METAFLOW_BATCH_EMIT_TAGS

feature so that - 1. It also adds tags for

metaflow.project

and

metaflow.branch_name

properties? 2. Some form of user-specified tags at deploy time? I want to also tag my ECS tasks with some attributes like

environment:production/experimentation

for cost exploration purposes. I am able to workaround this for now by filtering by ecs cluster in cost explorer, but it would be a useful addition if possible.

sure we can look into adding

project_name

and

branch_name

. The issue with forwarding user-specified metaflow tags to AWS is the validation that needs to be performed to obey to AWS's tag constraints. we can look into forwarding a sanitized version.