This repository contains the configuration parameters for the Cloudprem infrastructure of each environment. Each directory represents one environment (e.g. development) and contains parameters such as the version of the infrastructure and the inputs for the Terraform stack.
The infrastructure is managed and deployed using Terragrunt. By using terragrunt we are able to deploy the infrastructure to multiple environments, lock and version the infrastructure and keep Terraform code and state configuration DRY.
The outer terragrunt.hcl file contains configurations for the backend state and locks. The terragrunt.hcl files under each environment directory contain the parameters for that specific environment and the location and version of the Terraform code.
To deploy the stack, perform the following steps:
-
Initialize the backend and install the required providers and modules using terragrunt:
$ cd development $ terragrun init
Terragrunt will use the envrionment variable
AWS_REGIONto configure the S3/DynamoDB backend. If not specified will default to us-west-2 -
Review the parameters in the terragrunt.hcl file and execute the plan/apply
$ terragrunt apply
To delete the infrastructure for the environment execute terragrunt destroy
$ terragrunt destroy(Note: Terragrunt uses the directory name as part of the key for the state file, don't use the same directory for different environments, that can cause issues with the Terraform state, instead copy the configuration file into a new directory)
You can also deploy some pre-packaged CodePipeline pipelines to streamline the deployment process. For more information check the Cloudprem Pipelines repository