Is `exclude paths` relative to the path of the project or th

Question

Is `exclude paths` relative to the path of the project or the root of where it s being told to run

little-author-61621 · Answer

path of project

kind-angle-62935 · Answer

And there is currently still no way to tell infracost to not recursively try to detect things to run on run on this dir and that s it

white-airport-8778 · Answer

< kind angle 62935> I added an in case that s helps ```include all paths true```

kind-angle-62935 · Answer

Yeah I guess I m not really groking what `include all paths` does By default it s `false` But if it s `false` by default infracost still recursively runs

white-airport-8778 · Answer

An example might help I ll keep tweaking the docs Given the following config file the CLI goes down to 10 levels deep in the `dev` dir to find terraform files ```version 0 1 projects path dev include all paths true``` Without `include all paths true` only the `dev` directory is checked for terraform files

kind-angle-62935 · Answer

Is `include all paths` `true` by default

kind-angle-62935 · Answer

What would you expect to happen with the following ```version 0 1 projects path dev include all paths false path dev bar include all paths false```

white-airport-8778 · Answer

Sorry I forgot about the root vs non root modules ignore my previous answer `include all paths true` tells the CLI path autodetect function to use all directories i e root and non root modules with valid project files down to a max depth of 10 directories By default Infracost will try to autodetect only root Terraform modules Setting this to true includes subdirectories that we detect as modules instead of only root modules I ll keep iterating on the docs