The contents of the terragrunt file at module level

[suchona.kani.z]

The most important is the terragrunt.hcl file in the cloud provider folder or the Terragrunt root file. This is where you can centrally specify the Terraform providers you want to use, their versions and your remote backend. Each time you deploy a module, Terragrunt dynamically creates the corresponding Terraform files and places them in the directory where you run the code. This saves you the tedious and error-prone task of re-creating these default files over and over again.

The terragrunt.hcl file also allows you to set global variables that are valid for all environments and modules - for example, the tag managed_by = terraform or location = westeurope. This is ideal for defining variables once and then using them everywhere.

The Terragrunt env file
In addition to the root terragrunt.hcl file, there is an env.hcl file in each environment folder - dev, tst and prd. Here you can set variables that are only valid at the environment level and are shared by all modules within it. They are great for setting project or subscription IDs, name prefixes or environment-specific settings such as computing and networking options.

The Terragrunt module file
Finally, there is the terragrunt.hcl file within each module. This file connects the generic Terraform modules with their respective configuration files to create a real-world instantiation of the module in your kuwait consumer email list cloud environment. Here, it is helpful to think of the Terraform modules as callable functions with different arguments and the configuration files as the corresponding arguments. Each terragrunt.hcl module in this analogy is the place where the function (the generic module) is called with the argument values ​​(configuration files) to produce an output (infrastructure).


An analogy of Terraform modules as functions

Another great feature of terragrunt.hcl files is that they allow you to declare dependencies between modules. This not only makes the relationships between modules transparent – ​​it also makes it easier to connect modules to each other.

Terragrunt is a powerful tool that allows you to create Terraform projects that are much easier to maintain, especially as your project gets larger and more complex. Working with Terragrunt may be strange at first, but you will find that it makes your Infrastructure-as-Code projects better and easier in every way.

Conclusion
As Terraform projects grow in size, they become increasingly chaotic. This is because it becomes increasingly difficult to manage all the code and its configuration. To keep track of your infrastructure and manage it effectively, flexibly and consistently, you need a reliable project structure. Depending on the size and complexity of your project, this is not a trivial task, as you may have to make decisions and compromises that can come back to haunt you later.

The project structure I outlined in this article has served me and my colleagues well in managing these types of projects - often enterprise projects. I hope you can take something useful from my blog post and use it for yourself, because every project configuration is unique in its own way.

You can find more exciting blog posts from the adesso world in our previously published blog posts .