Import and round-trip
Import an Argo manifest, edit it on the canvas, and export it. The new file differs only where you changed something, plus some formatting.
Import a manifest
Section titled “Import a manifest”Open the workflow menu and choose Import. There are up to four tabs:
- Open one on the canvas replaces the canvas with one Workflow, WorkflowTemplate, ClusterWorkflowTemplate or CronWorkflow.
- Save many as workflows saves several manifests (split by
---, or as.yamlfiles) as workflows. The canvas isn’t touched. - From GitHub shows when the Dagweave GitHub App can reach a repository. It links every Argo manifest in it, or under a path you give, so Dagweave follows the repo. See WorkflowTemplates from Git. Untick Keep in sync with Git to copy them once instead.
- From cluster shows when you have a connected cluster. Pick a Cluster and namespace, then choose which WorkflowTemplates and CronWorkflows to import.


Paste your YAML into Open one on the canvas and click Import. With unsaved changes on the canvas, click Replace canvas to confirm.
No manifest handy? Open a blueprint from Library in the workflow menu.
Edit on the canvas
Section titled “Edit on the canvas”Select a step and change it in the panel on the right, such as its image or its Only run this when… condition. You can also add a parameter or a loop. To change the output kind, click empty canvas and set Output kind.
A step that calls a WorkflowTemplate through templateRef can be opened to see its
steps: double-click it, or select it and choose Open WorkflowTemplate. If
Dagweave doesn’t have that WorkflowTemplate, it says so.
Export the YAML
Section titled “Export the YAML”Open the caret next to Run and choose Get YAML. There are two views:
- Single file (editable) is the whole workflow as one manifest. It follows the canvas, and your YAML edits go back onto the canvas. Discard my YAML edits undoes them.
- Split into WorkflowTemplates (read-only) puts each reusable step in its own WorkflowTemplate.
Both have Copy and Download. Apply the file like the rest of your YAML:
kubectl apply -f my-workflow.yaml# or, for a one-off runargo submit my-workflow.yamlWhat survives the round trip
Section titled “What survives the round trip”- The kind. A WorkflowTemplate comes back as a WorkflowTemplate.
- Templates with no Dagweave step type, exactly as written.
- Containers and the entrypoint.
- Each task’s arguments, so a shared template still gets the right values from every caller.
generateNameand workflow parameters.- Template and task names. A template called
sayis stillsay.
Empty fields and ones Kubernetes adds, like creationTimestamp: null, are
dropped.
The export adds one annotation, dagweave/step-types. Argo ignores it, and
files without it still import.
On every push, the test suite round-trips 210 example files from the Argo Workflows repository, and CI fails if any errors. Of their 221 manifests, 221 come back with no field lost.
What changes: comments and formatting are lost, key order and quote style can
differ, and a workflow written with steps comes back as a dag.
Next steps
Section titled “Next steps”- Push the YAML to a Git repository instead of copying it.
- Connect a cluster and add a trigger to run it from Dagweave.