#Is it possible to ignore the `**/vendor/` directory upload when invoking Dagger?

1 messages · Page 1 of 1 (latest)

marble brook
#

I have a rather large vendor/ directory to work with. I've noticed Dagger calls slowing down significantly and found the culprit to be that Dagger includes **/vendor/ as part of it's required paths. I see this as a TODO item, but was wondering why this is required? And, if it's at all possible to avoid this expensive upload?

lapis timber
#

Try adding it to your exclude list in dagger.json.

marble brook
#

Oh, perfect. Thanks for pointing me to the tracking issues

onyx mist
#

@marble brook as a reference there's a stopgap today you can follow which is to add an exclude property in your dagger.json as well as the ignore filters in your pipeline. https://docs.dagger.io/api/filters

Directory Filters | Dagger

When you pass a directory to a Dagger Function as argument, Dagger uploads everything in that directory tree to the Dagger Engine. For large monorepos or directories containing large-sized files, this can significantly slow down your Dagger Function while filesystem contents are transferred. To mitigate this problem, Dagger lets you apply filter...