#terragrunt (2019-09)

Hi guys! @loren Have you found a solution to this https://github.com/gruntwork-io/terragrunt/issues/785 ? I wonder how people are solving odd (“new”) behavior of init hooks?

solve? no… workaround, yes… it’s not pretty

basically just gitignoring the copied file

in terragrunt.hcl

  after_hook "provider" {
    commands = ["init-from-module"]
    execute  = ["cp", "${get_terragrunt_dir()}/../../provider.tf", "."]
  }

in .gitignore

# Terragrunt files copied by hooks
dev/**/provider.tf

i tried your workaround of having a hook delete the file, but turns out we actually need it there because terragrunt tracks the files it copies from the terragrunt dir to its cache working dir, and purges anything from the cache working dir that it didn’t copy

Great, I ~solved~orkaround it exactly as you said. I am not sure there will be a proper fix in the near future. It starts to look a big ugly here and there with terragrunt…

yeah, i think we need the workflow to be part of terragrunt proper, rather than implemented with hooks

it’s not something the gruntwork folks do, so they just don’t see it as a real use case at the moment

As another not elegant hack I can run terragrunt plan --terragrunt-source-update to get source reinitiated every time, then I can have after_hook which will remove the file.

Right, yeah, that also works, but is slow

Hi guys!, does anyone know how to solve dependencies between modules without having to run a terragrunt plan-all from the root directory? This is our current directory structure

root
├── dynamodb
│   ├── TableOneDir
│   │   └── terragrunt.hcl
│   ├── TableTwoDir
│   │   └── terragrunt.hcl
├── lambda
│   ├── LambdaOneDir
│   │   └── terragrunt.hcl
│   ├── LambdaTwoDir
│   │   └── terragrunt.hcl
├── secrets
│   └── terragrunt.hcl
├── sns
│   └── terragrunt.hcl
└── terragrunt.hcl

We need to run plan only in the LambdaOne directory and auto resolve a dependecy of a TableOneDir existing.

Also this are out hcl examples

terraform {
  source = "git::[email protected]:Company/core-of-sources.git//lambda/LambdaOneDir?ref=branch-one"
}

# Include all settings from the root terragrunt.hcl file
include {
  path = find_in_parent_folders()
}

# Dependencies
dependencies {
  paths = ["../../dynamodb/TableOneDir"]
}

quick question

• terragrunt –version /var/lib/jenkins/workspace/gc-vitr-landing-page_master@tmp/durable-dfb884a1/script.sh: line 1: terragrunt: command not found [Pipeline] } —- Have this error in my Jenkins build…. have any one come across this ever ?

@Sharanya is terragrunt in your path ?

in the PATH or is installed

+1

i dont think terragrunt in installed on the server

You will need to install it