#Module config (dagger.json) include-behaviour(?)

1 messages · Page 1 of 1 (latest)

tired arch
#

Hey there. Trying to migrate my typescript-sdk dagger pipelines to dagger modules. Therefore I have a (big mono-)repo/project root with the following structure:

% ls -al
drwxr-xr-x@ 42 me  staff   1344 21 Nov 19:16 .
drwxr-xr-x@  9 me  staff    288 14 Nov 15:42 ..
drwxr-xr-x@ 10 me  staff    320 21 Nov 18:58 .dagger
drwxr-xr-x@ 10 me  staff    200 21 Nov 18:58 dagger.json
drwxr-xr-x@ 47 me  staff   1504 21 Nov 17:23 pipelines
...

Idea is that the new module would (for now) use code from the pipelines-directory (without moving/breaking them). Therefore I'd like to use the "include" feature:

dagger.json

{
  "$schema": "https://docs.dagger.io/reference/dagger.schema.json",
  "name": "my-project",
  "engineVersion": "v0.19.7",
  "sdk": {
    "source": "typescript",
    "debug": true
  },
  "include": [
    "pipelines"
  ],
  "source": ".dagger",
  "disableDefaultFunctionCaching": false
}

With this configuration, I end up in the debug shell with the following content of (/src)

dagger /src $ ls -al
total 20
drwxr-xr-x root     Nov 21 19:16 .
drwxr-xr-x root     Nov 21 19:20 ..
drwxr-xr-x root     Nov 21 19:20 .dagger

I would have expected that this directory would contain the mounted pipelines directory from my project root. I have tried variations of include with:

  • /pipelines
  • pipelines/
  • pipelines/**
    ...

What I have also noticed, that trying "../pipelines" (assuming the import is relative to the .source: .dagger directory), I get the following error:
! include/exclude path "../pipelines/**" escapes context

Crazy thing is, I thought I would have it working at some point. Maybe it broke with a new engine version? I am currently on v0.19.7 (also for the fresh debug feature).

Error that led me here was
Error: File ../pipelines/tsconfig.json not found.
because I'd try to let my dagger.json typescript module base on the pipelines/tsconfig.json (and only override the compilerOptions.path).

Any help is appreciated. 🙂

#

Module config (dagger.json) include-behaviour(?)

#

Was trying to follow this doc: https://docs.dagger.io/reference/configuration/modules/#:~:text=The JSON schema for the Dagger module configuration file dagger.json supports an include field. It tells the Dagger Engine of additional files to include or exclude when loading the module itself. By default%2C only dagger.json and all files under the module's source directory are included.

Module Configuration | Dagger

Learn how to configure Dagger modules, including TypeScript SDK settings, file filters, and alternative runtimes.

small leaf
small leaf