Savin

I thought this was handled. Let me take a look.

I was unable to reproduce the error using Metaflow 2.6.0 Click to expand! ``` { "apiVersion": "argoproj.io/v1alpha1", "kind": "WorkflowTemplate", "metadata": { "name": "helloargoflow", "namespace": "default", "labels": { "app.kubernetes.io/name": "metaflow-flow", "app.kubernetes.io/part-of":...

What is the version of Argo Workflows you are on?

Aha - the UI has an additional check that prevents uploading the JSON by hand.

I have started a [thread](https://cloud-native.slack.com/archives/C01QW9QSSSK/p1652298821097089) in CNCF slack to ensure that this isn't a regression within Argo Workflows UI.

@ZiminPark Are you running into this issue when you submit using the UI?

Good point. We should add that to the docs.

@pombredanne What would be the expected behaviour of such support? Currently, we create isolated environments for every step and many data science packages have system package dependencies which pip cannot...

@philipphager The `@conda` decorator, currently, does much more than just setting up the needed conda environment. On the backend, it snapshots the packages (including transitive dependencies) and appropriate metadata so...

@dgrahn We currently don't integrate with Slurm, but it's an interesting idea. @romain-intel Do you have any suggestions for Slurm alternatives for HPC workloads?