-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing behavior of --terragrunt-strict-include
when no --terragrunt-include-dir
flags are included
#1631
Fixing behavior of --terragrunt-strict-include
when no --terragrunt-include-dir
flags are included
#1631
Conversation
2aa1e8d
to
90d7e69
Compare
--terragrunt-strict-include
when no --terragrunt-include-dir
flags are included--terragrunt-strict-include
when no --terragrunt-include-dir
flags are included
Added in basic tests for this behavior and was able to get them to pass locally on my machine after a minor change as Go wasn't picking up the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes LGTM, thank you!
One minor request: would you mind updating the docs to make it clear what the behavior will be?
@brikis98 Yep, I'll find some time to do that later tonight or tomorrow, thanks! |
@brikis98 Added a statement to the docs about the new behavior of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! I'll kick off tests now.
Tests passed! Merging now. |
This PR is an attempt to fix the behavior of Terragrunt when the
--terragrunt-strict-include
flag is supplied without any--terragrunt-include-dir
flags.The expected behavior is that Terragrunt will evaluate to not run on any modules in this case, but the current behavior is that it will run over all modules of the working directory.
This is to address #1600.