terragrunt-infrastructure-live-example VS flux2-kustomize-helm-example

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.

Any public repo show-casing a nice structure? (I am used to the Gitops world on K8s, and for the case of FluxCD for instance I would recommend this repo as a good practice to start multi-tenancy. https://github.com/fluxcd/flux2-kustomize-helm-example. I am looking for a similar "boilerplate" but for TF 😅)

My recommendation would be to take a look at their documented example of this exact scenario with various overlays for production and staging, but you could ofc add as many as you wanted. All you would do is for production point flux to the production overlay/ directory, which then calls all your normal files but overrides some values you desire. Further to this you can keep your helm chart focused on lets say the "most-common" use case, then just call it with whatever additional values you would like, E.G here in the same repo as above. Notice the values at the bottom of the yaml file which override the charts default values.

Here's an example using flux v2 to deploy to multiple environments/clusters: https://github.com/fluxcd/flux2-kustomize-helm-example

We are using flux2, which uses Kustomize under the hood. It takes a little bit of time to learn about the different CRD's which are available but once you do it works excellent. They also have an example project which sounds like it might fit your use case https://github.com/fluxcd/flux2-kustomize-helm-example

As /u/vincentdesmet mentioned Kustomize will most likely to solve your many "apps" with slightly difference issue, this is a good example https://github.com/fluxcd/flux2-kustomize-helm-example (also include helm one)