Artifacts

Your workflow outputs, without leaving dagweave.

Reports, plots, CSVs, logs and PDFs open in the run that produced them. The files stay in your own storage.

The problem

Seeing the output means giving people the Argo UI.

The Argo Workflows UI shows artifacts. Getting somebody to them means an account on it, a role binding, and a route in from outside the cluster.

So the people who want the output are the people you have to onboard to Kubernetes, or you fetch it out of the bucket and send it to them yourself.

In the page

View your workflow artifacts directly inside dagweave

No need to leave dagweave to see the outputs from your workflows. Reports, plots, CSVs, JSON, logs and PDFs open in the run detail.

Every file a run wrote is listed on that run, with its size and type.

Untrusted by default

Open a report without trusting what is in it

A workflow can write a report with scripts in it. dagweave opens it in a sandbox, so it cannot reach your account.

A report cannot read your dagweave account or reach your cluster.

Where the bytes are

Artifacts remain in your storage, nothing is stored on dagweave's end

dagweave reads the object through the connector already running on your cluster.

Your storage credentials stay in your cluster.
Delete a file in your bucket and dagweave cannot open it. The run goes on listing what it wrote, because that row is the record and we never held the file.

what the run row holds, per artifacttext

name           as declared in the workflow spec
bucket         yours
key            yours
size           what a HEAD answered when the status was reported,
               and unset when nobody got an answer
content type   what your store said, advisory, never echoed back

the object itself
               not held, not copied, not cached

Who can read it

Nobody needs an Argo UI account to read a result

Your analysts open the report in dagweave, without a role binding, a kubeconfig, or an account on the Argo Workflows UI.

Anyone on the team opens what a run produced, without a kubeconfig or an account on the cluster.
Every artifact opened is recorded in the audit log, against the run it came from.

Stop fetching your own output out of S3.

dagweave is in early access. Leave an email and we will bring you on as we open it up.