Savin

please see - https://outerbounds.com/blog/metaflow-in-notebooks-and-scripts/

Makes sense. Although not all resources can be tagged by Metaflow - for example, the underlying ECS instances used by AWS Batch can't be tagged because they will time-share with...

metaflow [sets tags on all AWS Batch jobs](https://github.com/Netflix/metaflow/pull/631/files) which AWS takes into account for cost reporting.

Another option could be to first begin with ``` python flow.py step-functions create --notify-on-error [email protected] --notify-on-success [email protected] ``` This is the pattern that we follow with `meson` internally. Implementing `notify-on-failure`...

`python flow.py argo-workflows create --notify-on-error [email protected] --notify-on-success [email protected]` has been available for a while now, so perhaps this issue can be closed. @jaskaran-virdi-imprivata - One mechanism would be to use...

this use case is now well supported using our [runner and deployer](https://docs.metaflow.org/metaflow/managing-flows/introduction) apis

@vamagithub Given that this change is going to be backwards incompatible, rather than making the change here, what do you think of making the change in the `main_cli.py` instead to...

Thanks for opening the issue! We will look into it.

Original thread on [gitter](https://gitter.im/metaflow_org/community?at=611566f94bfde341d95839cc).

sure if you want to start a gdoc, that will be great!