How to configure additional project globs

When your Terraform stack depends on folders located outside your project root directory, you need to configure additional project globs to ensure the stack/module triggers when files within that path changes change.

Example setting up project globs for modules

If your project root is infra/terraform/dev/ and you use modules in infra/terraform/modules/, you should set your additional project glob to:

infra/terraform/modules/**

This pattern will trigger your stack when any file or directory within the modules directory changes, including all subdirectories and files.

Common project glob patterns

Here are the most useful patterns for configuring project globs:

• Any directory or file: **

• A directory and all of its content: dir/*

• A directory path and all of its subdirectories and files: dir/**

• Match all files with a specific extension: dir/*.tf

• Match files with specific patterns: data-???-report (matches three characters between "data" and "report")

• Match files with character sequences: dir/instance[0-9].tf

What doesn't work

Simply using the directory path without wildcards (e.g., infra/terraform/modules) will not work as it won't be classified as a match for changes within that directory.

Testing your patterns

You can test your project glob patterns using the policy workbench to ensure they work as expected before applying them to your stack.

For more detailed information about project globs, refer to the official documentation.