#terragrunt (2020-02)
Terragrunt discussions
Archive: https://archive.sweetops.com/terragrunt/
2020-02-21
@scorebot help keep tabs!
@scorebot has joined the channel
Thanks for adding me emojis used in this channel are now worth points.
Wondering what I can do? try @scorebot help
2020-02-25
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…
e.g. it can end up running something like terraform apply -lock-timeout=30m tfplan -input=false -auto-approve -no-color which isn’t valid.
blame points to this issue, with the linked pr, https://github.com/gruntwork-io/terragrunt/issues/386
Yeah, I’ve opened a PR
that has royally fucked with my plan.
wow, a terragrunt room. amazing.
I just found this room and thought the same thing!
haha welcome
Also, we have archives available here: http://archive.sweetops.com/terragrunt/
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.
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.
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
}
ahhhh haaaa
ammmmazing. thank you so much.