#terragrunt - February 2020

terragruntArchived
10 messages

Terragrunt discussions
Archive: https://archive.sweetops.com/terragrunt/

February 2020
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)over 6 years ago
@UUB28NLDS help keep tabs! 😉
joshmyers
joshmyersover 6 years ago
Anyone know why https://github.com/gruntwork-io/terragrunt/blob/master/configstack/stack.go#L77 is auto setting those args if using xxx-all rather than letting you set those via extra_args or whatever. They don’t get deduped and end up breaking extra_args if using plan output…
joey
joeyover 6 years ago
wow, a terragrunt room. amazing.
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)over 6 years ago
haha welcome 😃
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse)over 6 years ago
Also, we have archives available here: http://archive.sweetops.com/terragrunt/
joey
joeyover 6 years ago(edited)
if anyone has pointers on why terragrunt would not be writing outputs when i'm using a module indirectly, that'd be totally rad. https://community.gruntwork.io/t/terragrunt-not-writing-outputs/410 .. https://community.gruntwork.io/t/examples-of-3-tier-module-structure/408 .. i'm sure i'm doing some silly bonehead mistake. whereas i need to go test my helmfile question more, this one was less clear to me. 🙂
loren
lorenover 6 years ago
it's really just a terraform thing. you have a root module (what you are calling a "unit") calling a another module. terraform requires that the root module must declare its own outputs. outputs from nested modules are not automatically propagated in the root module's outputs.
loren
lorenover 6 years ago(edited)
try this in your unit to output everything from the nested vpc module... you can scope it more and create multiple outputs if you don't need everything
output "vpc" {
  value = module.vpc
}
joey
joeyover 6 years ago
ahhhh haaaa
joey
joeyover 6 years ago
ammmmazing. thank you so much. 🙂