generate_projects
directive in digger.yml. Digger will then traverse the directory according to include_patters
and exclude_patterns
provided and dynamically generate the list of projects
include_patterns
, exclude_patterns
and include
, exclude
.
include
and exclude
are used to decide which project get generated in the first place
whereas include_patterns
and exclude_patterns
are used to decide which additional folders should cause the generated project to trigger
Demo repo
traverse_to_nested_projects
to generate a project for all sub-directories:
false
, only the first directory with a .tf file will be evaluated.
terragrunt: true
for each block. Normally you would only have one terragrunt structure and so you will have
one block entry. However you may be also interested to specify different structure and different parameters
for different folders. For example, you may have a dev, staging and prod account hierarchy and therefore you
would specify the blocks in that way. Alternatively maybe you have different providers and you would like to
specify those different providers as well. Note that for very large terragrunt monorepos segragating by blocks
will lead to improved performance since it will not unnecessarily traverse an entire tree if no files have been
changed within it.