
As a DevOps Engineer or Infrastructure Management team, we need to handle Multiple environments for Multiple or Single target provider like AWS
So to fill this gap which Terraform can't handle complex environment using workspace feature, we are using Terragrunt to keep out Terraform code DRY
How to download Oracle VirtualBox to perform practical sessions on local machine?
Please check the link
Download Ubuntu 22.04 LTS version or 20.04 LTS version server from the links
Note: Do not use Desktop version, use only server
VS Code Download
Terragrunt tool is a thin wrapper around Terraform which will simply the Job of Infrastructure like AWS Cloud etc., when we want to manage multiple environments
As DevOps and SRE engineer, we need to manage multiple targets and each target provider will have multiple environments for which it become complex to manage
Writing Terraform Configuration files to store in GitHub
Understanding Terragrunt configuration files for multi-environment infrastructure
Terraform workspace and modules limitations
We will be using AWS Cloud as target provider in this course
We have created two scenarios, VPC network and EKS Cluster with Node Group using modules
Understanding terragrunt blocks and attributes
You need to have some basic understanding on Terraform prior to this course
We will not only talk about Terragrunt configuration files, we have to see from scratch how we need to write Terraform configuration files to keep DRY for Terragrunt for scenarios mentioned above
We can also manage multiple AWS accounts with ease
Terragrunt is opensource tool, which provides flexibility to contribute to the development as well
In terraform configuration files, we will use multiple built-in functions as well to add some logic for resource management
Terragrunt is trying to add more functionalities as well to provide visibility to different target providers not only for AWS specific
Finally we will see all the terragrunt commands to manage and how terraform commands options are inherited by terragrunt cli