Code
Terraform modules allow you to reuse code and configurations across projects and environments, making it easier to maintain and scale your infrastructure. Modules are a way to encapsulate and abstract your infrastructure code, providing a higher level of abstraction than individual resources.
To use a module in your Terraform code, you need to define a module block that references the module’s source location. The source location can be a local file path or a remote URL, such as a Git repository or Terraform Registry module. Here’s an example of a module block
module "vpc" {
source = "git::https://github.com/example/vpc-module.git"
vpc_cidr = "10.0.0.0/16"
public_subnets_cidr = ["10.0.1.0/24", "10.0.2.0/24"]
private_subnets_cidr = ["10.0.10.0/24", "10.0.20.0/24"]
}
In this example, we’re using a module named vpc that’s located in a Git repository at https://github.com/example/vpc-module.git. We’re passing in some input variables for the module, including the VPC CIDR block and the CIDR blocks for the public and private subnets.
When you run terraform apply, Terraform will download the module from the specified source location and use it to create the resources defined in the module. You can also use the module block multiple times to create multiple instances of the same module with different input variables.
To create your own modules, you can follow the same file structure and best practices outlined in the previous answer. Once you’ve created a module, you can publish it to the Terraform Registry or a Git repository, making it available to others for reuse.
Overall, using Terraform modules can help you write more modular, reusable, and maintainable infrastructure code, making it easier to manage your infrastructure at scale.
