Allow arbitrary AWS tags based on metaflow config or batch decorator #1627
Comments
Limess
added a commit
to Limess/metaflow
that referenced
this issue
Nov 8, 2023
Limess
added a commit
to Limess/metaflow
that referenced
this issue
Nov 8, 2023
Limess
added a commit
to Limess/metaflow
that referenced
this issue
Nov 8, 2023
|
This is needed for Autodesk usage as well, as we have many new teams use Metaflow and need a way to manage EC2 tags per user/team via the |
|
This looks like a great feature to have! |
|
+1 my org uses standardised attribution tags across all the cloud infra, would want to be able to automatically tag metaflow resources with the standard org tags for the parent project, not just metaflow's own metadata tags |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some cost allocation tags we'd like to add which are not tied to a given user.
As such, we'd like to be able to tag and then allocate AWS batch usage from metaflow correctly based on these tags.
Currently Metaflow supports
METAFLOW_BATCH_EMIT_TAGSbut this only supports['metaflow.flow_name', 'metaflow.run_id', 'metaflow.step_name', 'metaflow.version', 'metaflow.run_id.$', 'metaflow.user', 'metaflow.owner', 'metaflow.production_token'](https://github.com/Netflix/metaflow/pull/631/files).Ideally it'd be great to be able to do this both at the metaflow config level (so a team can set/forget it) and in the
@batchdecorator, but the latter would be the most useful.The text was updated successfully, but these errors were encountered: