Terragrunt discussions Archive: https://archive.sweetops.com/terragrunt/
HI all, just . quick one, I need some help installing terragrunt v18 on mac os, I’ve managed to do it via brew but that installs a dependancy of terraform v12 (i need v11). I went to releases, but not sure how to install Darwin_64 on mac? Any ideas, thanks
@Nehal You can remove terraform after it has been installed by terragrunt, or use
tfenv to manage terraform installation.
thanks..didn’t know about tfenv, look into it
Hi @loren Have you thought best practices yet for running pre-0.19 with post 0.19 ? Seperate tree structure for post 0.19, or having both .tfvars and .hcl in one structure.
Use direnv with envrc :-)
In a geodesic shell, of course
Hi Erik! For the binaries i see that working, but not so much for the tfvars / .hcl implementqtion
Our strategy is that a given folder should only use one version of terraform. It doesn’t make sense to have 2 versions of terraform in the same project folder
I guess the problem with terragrunt is you have it operate across folders of different versions?
A project folder for us is a root module
well with terragrunt you can have a tree model with tfvars inheritance more or less, provider, account and region specific information can be autofilled this way. But this does mean that the tree is being traversed and being searched for other specific tfvars. From 0.19 this information is not in tfvars anymore but in .hcl, so in case one wants to slowly move certain root modules in this structure to v0.19/tf 0.12 that is something to be taken care of.
I wanted to be able to update quickly to tf 0.12 but with backwards compatible module changes, then leisurely update modules to take advantage of new syntax. Unfortunately there are just way too many, very basic (IMO) backwards incompatible changes in tf 0.12
So now it’s likely to be quite a while before we update active root configs to tf 0.12 since we have to go all in to do it
Also means probably won’t be using terragrunt 0.19 until then, and when we do we will also begin using it across all configs in the project simultaneously
Sucks because I want to use tf 0.12 now, but the backwards incompatibility means we won’t be able to adopt it for quite some time
So I guess, to answer the actual question, no, I haven’t thought about how to use tg 0.19 and tg <0.19 in the same project since at the moment I’m expecting eventually we’ll update everything at once
Thanks, sounds like you’re stuck with the same problem, and probably means we need to start with 0.12
Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules. - gruntwork-io/terragrunt
0.12 support on the way… https://github.com/gruntwork-io/terragrunt/pull/731
This PR upgrades Terragrunt to work with Terraform 0.12. Key changes: We are migrating from having the Terragrunt configuration in terraform.tfvars to terragrunt.hcl. This is necessary because Te…