Savin

@Dana-Farber The [PR](https://github.com/Netflix/metaflow/pull/1091) is now available for testing.

@davified there are a few different ways to achieve this. - If all your jobs are running on AWS Batch (or AWS Step Functions) - you can rely on CloudWatch...

Would `notify_ci(self.param_a)` work for you?

This indeed looks like a bug that should be fixed.

This isn't needed any more.

Not in a straightforward manner. There is an open ticket #571 to add them to the `current` object. One immediate workaround would be to launch your workflow as `METAFLOW_MAX_WORKERS=100 python...

I can get a PR out next week? Would that work?

Good point! Do you think `@docker` would be a better terminology? Or maybe `@image(name='foo')`? Regarding executing locally, one idea that we have been toying with is introducing `--environment=docker` that will...

We should move forward with `@image`. The [k8s container spec](https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/V1Container.md) assembles the entire container which is what Metaflow does on behalf of the user, so `@image` feels more natural to...

For backward compatibility, we would have to ensure the correctness of `@batch(image='blah')`