terragrunt-infrastructure-live-example VS terrafunk

In the official Terragrunt documentation there is a good article about how to set up a Terragrunt project and where to place modules. In fact, there is also a repository on GitHub providing an example project on how the creators recommend setting up Terragrunt. I certainly recommend going through that repository, because it is a good reference for a starting point. Having that said, I like to structure mine a little bit differently. My recommendation is to have different AWS accounts for each environment. Getting a new account usually is relatively easy to accomplish even if we are working in a corporate environment (your workplace most likely is using AWS Organizations to manage accounts). The existence of multiple accounts does not require additional costs, we only pay for what we use.

NOTE: More information about the terragrunt.hcl file can be found in this example repository.

Here's a pointer to an example repository with a Terragrunt monorepo (good, easy to manage), and each module called gets its unique statefile (good, smaller blast radius) where the tradeoff is learning a new tool and paradigm: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example.

I also highly recommend to check out how terragrunt recommends structuring your repo and even further details on this documentation page.

https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/_envcommon/mysql.hcl https://terragrunt.gruntwork.io/docs/features/keep-your-terraform-code-dry/

did you have a look at this example? https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/terragrunt.hcl

Terragrunt! Using a scaffolding approach like this for inspiration https://github.com/gruntwork-io/terragrunt-infrastructure-live-example

I would recommend taking a look at the example repo here: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example. The layout you have doesn't look like a structure that would work well with terragrunt.

A good example is in gruntwork-io / terragrunt-infrastructure-live-example repository and further documentation on Terragrunt's own documentation page.

Also, thanks for the link. Hadn't seen that solution before. Going to play around with that some when I have some time, it actually looks fairly similar to some of the stuff I do with my terragrunt templates. We use common yaml variables. And then I have some simple routines that do "deep merging" that allow you to have a huge level of granularity on how you can override them. Then more levels of overrides so you can hit individual resources inside of the stack. It's almost like a poor man's hiera to a degree. Then another helper utility called terrafunk that allows you to test this whole data layer super rapidly: TerrafunkAlways happy to take a look at other solutions I can borrow some ideas from. :)