-
-
Notifications
You must be signed in to change notification settings - Fork 995
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
Terragrunt run-all evaluates locals of not included modules when --terragrunt-strict-include is used #2860
Comments
Any news on this? It breaks the entire deployment as in our case staging has no key to production sops file and vice versa |
Hi. Are there any news with PR for this bug? I have really ugly workarounds in my TG modules because of this (filling not needed env variables with fake values in unrelated modules). |
https://gist.github.com/egorksv/65ab1a1ab8bc5cfdb7b3a6330e90b5af Workaround script to force include specific modules
|
I just started to see "new" version of this bug.
In effect, I need to to provide to terragrunt env variables of modules which I don't want to deploy. I wanted only my "datacollector" application to be redeployed, and I've got errors about cluster that was not expected to be touched:
TG version: v0.55.19 |
Hi, regarding the PR #3012 Just a question, would it also address dependency evaluation of the terragrunt stack, and not just locals evaluation? For my use case, I append a However, since Terragrunt currently does not fully respect the e.g. It really should fully respect the strict flags and not even evaluate it in the first place |
Hi @denis256. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for raising this issue. |
Terragrunt run-all evaluates locals of not included modules when --terragrunt-strict-include is used
The text was updated successfully, but these errors were encountered: