Open fleroux514 opened 1 year ago
Thanks for reporting it @fleroux514 ! Indeed, modules_dir making sense Tagging @Spartakovic if you have any input on the way this should work?
there is probably no need to have module_dir, since we are going to parse tf files? otherwise seems like a great idea, i wonder if any other tool is doing that
@Spartakovic you are right :) no need to specify if digger is going to parse it anyways...
The last comment suggests the issue can be closed. Labeling as such - if someone disagrees please indicate in the next few days
not exactly, wanted functionality is still missing, it's just that solution suggested in the title is not the one preferred
Correct, just updated the title/description for this feature request.
bumping this issue up because this is still valid. Now with generate_projects and include/exclude pattern, part of this problem has been solved already. As an extension, I wish there is a way to tell digger to update all projects that rely on a module (referenced by relative path), plan and execute when there are changes inside the module
We are using a mono-repo, where different projects are reusing various modules specified under the
./modules
directory which contains 10+ modules.In each project, I currently need to do a manual verification of which modules are being used, in order to specify them statically using the
include_patterns
project config. And if we eventually start using a new Terraform module in a project, there is a good chance we might forget to update digger.yml accordingly while doing so. So the current workflow is very error prone.Digger should dynamically detect module directories without the need to specify them using
include_patterns
.In the following code snippet, Digger could scan the code and detect that the "vpn-ha" module is being used in this case.
./envs/dev/main.tf