WorkflowTemplates from Git

If your WorkflowTemplates live in a Git repo and a GitOps tool like Argo CD or Flux applies them to your cluster, link them instead of copying them into Dagweave. Dagweave then follows the repo, and the repo stays in charge.

Link a folder or a file

Open Import, choose From GitHub, and pick the repository, branch and path. Keep in sync with Git is ticked. A folder links every Argo resource in it, and a file links that one. Each file has to hold one resource.

Linking the same folder again picks up new files and follows files that moved.

Linked workflows show a Git mark in the Workflows list.

What stays in sync

Dagweave reads each file when you open it and after every push to the branch. The canvas shows the repository, file, branch and commit, and tells you when Git has something newer than what you’re looking at.

Editing

Git owns a linked file, so Dagweave doesn’t save your edits. Push to Git sends them back to the same file as a pull request or a commit. If someone changed the file since you opened it, the push stops and asks you to reload first.

Dagweave writes the file in its own layout, so comments in it are lost. Check the diff before you merge.

Running

Dagweave never installs a linked WorkflowTemplate on your cluster. That’s your GitOps tool’s job. A run submits a Workflow that refers to the WorkflowTemplate by name, with the parameters you give it. A required parameter with no default has to be given.

Each run records the Git commit it came from, and the run page links to the file at that commit.

The run is drawn as a graph, and a step that calls a WorkflowTemplate opens to show its steps.

When a file goes away or breaks

If a file is deleted or can’t be read, Dagweave keeps the last good version and says what happened. To edit a workflow in Dagweave again, unlink it. It then stops following Git.