Skip to content

Housekeeping

Clear out old runs with dagweave delete and remove the local cluster with dagweave prune.

Each run is a directory in your state directory:

System Runs directory
Linux $XDG_STATE_HOME/dagweave/runs, or ~/.local/state/dagweave/runs if that’s unset
macOS ~/Library/Application Support/dagweave/runs
Windows %LOCALAPPDATA%\dagweave\runs

Your secrets and the local cluster’s kubeconfig sit next to runs, in the dagweave directory.

Running a file again replaces its previous run, but each different workflow leaves its own directory. To delete one, pass a name from dagweave runs:

$ dagweave runs
Succeeded pipeline just now
$ dagweave delete pipeline
dagweave: pipeline is gone from this machine.
dagweave: its step output went with it, and nothing else had a copy.

dagweave delete --all deletes every run. Neither asks first or can be undone.

The local cluster stays up between runs, holding memory, and its image store grows with every image your steps pull. dagweave prune deletes the cluster, its disk and its image store. Runs and secrets stay. The next cluster run takes about two minutes to start a new one.

To remove a cluster other than the default, pass its name, such as dagweave prune my-cluster. It fails if there’s no cluster by that name.