Yves (eunomie) has an open PR — dagger/dagger#13130 — adding dagger module-checks, a new experimental command that fetches check/trace results from Dagger Cloud and renders them in the CLI. It works, but it's a separate command with its own rendering pipeline, disconnected from the existing dagger check.
Don't add a new command. Make dagger check smarter.
Running tracking doc for the original workspace-artifacts design session. Superseded by the Modules v2 design docs.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
Analysis concluding that typed collection filters collapse the need for a
separate artifact address concept. The conclusion is incorporated into
hack/designs/modules-v2/artifacts.md on the modules-v2 branch of
dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
Working notes from the design session that produced the Modules v2 split docs.
Covers the Artifacts API schema evolution, Execution Plans, filter model,
Action type, and staged changes to collections. Content has been absorbed into
hack/designs/modules-v2/ on the modules-v2 branch of dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
This document is archived. It was the original integrated design covering
collections, addresses, verbs, plans, and provenance as one system. It has
since been superseded by the split design docs in hack/designs/modules-v2/
on the modules-v2 branch of dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
Workspace design briefing: implementation vs. design discussion
Companion to the ongoing Discord design thread. Based on a review of the implementation on the workspace branch against the points raised in discussion.
Builds on Part 1: Module vs. Workspace and Part 2: Workspace API
Builds on Part 1: Workspaces and Modules