Re:HashiCorp’s multi-product strategy
by datatrashfire on Wednesday August 31, 2022 @12:42AM
(#32658451)
Terragrunt is an antipattern. Made the mistake once with a very poorly structured project I inherited, never again.
[ Parent
| on HN ]
Re:HashiCorp’s multi-product strategy
by mixedCase on Wednesday August 31, 2022 @01:16AM
(#32658636)
Terragrunt is not an anti-pattern, but it is a tool that is easier to get wrong than Terraform and so people create great messes with it.
Used right it's the only way to remain sane on any non-trivial set of infra where you don't end up hand-rolling a half-baked version of Terragrunt.
Re:HashiCorp’s multi-product strategy
by busterarm on Wednesday August 31, 2022 @03:23AM
(#32659344)
Managing 10^5 servers right now with Terragrunt. Can confirm, it's the only way to stay sane.
Getting to this point was a learning process though. Probably six solid years of investment now.
Re:HashiCorp’s multi-product strategy
by dilyevsky on Wednesday August 31, 2022 @04:05AM
(#32659605)
From experience terragrunt + atlantis has been much better experience than hashicorp's own terraform enterprise service.
Re:HashiCorp’s multi-product strategy
by busterarm on Wednesday August 31, 2022 @10:20AM
(#32662376)
not using terraform enterprise.
"Code generation" is pure evil.
I second that Terraform needs to work at least on dynamically specifying providerblocks. This is where people usually resort to terragrunt.
Workspaces and state layering are in my experience hard on the novices and unfortunately they turn to terragrunt.