-
-
Notifications
You must be signed in to change notification settings - Fork 955
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
Inconsistent cache behavior for TF modules (symlinking and copying) #896
Comments
I'm fairly certain this is a TF 0.12 feature, where it now detects whether multiple modules reference the same source and only downloads the source one time. Other module instances are symlinked to the downloaded copy (presuming the OS supports symlinks). However, now I cannot find the reference for that feature... Was either in a GitHub issue or one of the TF 0.12 blog entries... |
Here it is: hashicorp/terraform#11435 (comment) |
@lorengordon |
Do you get the exact same inconsistent behavior if you use |
@lorengordon Thank you both for your tips, I will recreate this issue on terraform repo. |
Terragrunt: 0.19.28
Terraform: 0.12.9
I observed some inconsistent cache behavior when I use multiple instances of the same terraform module (local modules with absolute paths).
For example, when I have definitions like this:
after
terragrunt init
my cache folder looks like that :
One instance of the module is symlinked and all others are copied. AFAIS this behavior is repeatable, always the same, and only one instance is symlinked. This applies to all other used TF modules.
Personally, I prefer symlinking over copying in that case, but more important is consisted behavior for all occurrences of the module because current situation produces hard-to-tracking side effects.
The text was updated successfully, but these errors were encountered: