AWS Terraform Meta Arguments

In my Day8/30 of learning and mastering AWS Terraform we dive deep into understanding what Terraform Mate Arguments are and how they are used. Meta Arguments are special arguments provided by Terraform itself to facilitate resource management beyond provider-specific configuration options.

What are Meta Arguments
Meta arguments in Terraform differ from provider-specific arguments; they are supplied by Terraform to enhance the logic and functionality of configurations without needing external scripts.

For example, if you are calling a module and want to reuse it five times, you do not copy and paste that block five times. You use a meta argument to tell Terraform to repeat it.

Meta arguments allow you to keep your code clean and predictable.

Three primary Meta Arguments covered:

• depends_on: Specifies explicit resource dependencies, controlling the order of resource provisioning to ensure correct sequencing.

• count: Functions as an iterator over lists to create multiple instances of a resource using a single block of configuration.
  Example; Lets try creating 2 S3 buckets using the count meta-argument.
  

resource "aws_s3_bucket" "example" {
  count = 2
  bucket = var.bucket_names[count.index]

  tags = var.tags
}

variable "bucket_names" {
    type = list(string)
    default = ["some-random-string1", "some-random-string2"]
}

 variable "tags" {
     type = map(string)
     description = "list of tags for EC2 instances"
     default = {
       Environment = "dev"
       Name = "dev-instance"
 }

• for_each: Iterates over sets or maps to provision resources for each element, enabling more flexible and dynamic resource creation compared to count.

resource "aws_s3_bucket" "example" {
  for_each = var.bucket_names
  bucket = each.value

  tags = var.tags
}

variable "bucket_names" {
    type = set(string)
    default = ["some-random-string1", "some-random-string2"]
}

 variable "tags" {
     type = map(string)
     description = "list of tags for EC2 instances"
     default = {
       Environment = "dev"
       Name = "dev-instance"
 } 

Difference between implicit and explicit dependencies:

Implicit dependencies; are automatically managed by Terraform based on references in configuration.
Explicit dependencies; are manually declared using depends_on to set precise execution order.

Detailed Explanation of Meta Arguments

1. depends_on This Explicitly defines resource dependencies, its N/A to any dta type, and it Forces Terraform to wait for specified resources before creating dependent resources
2. count Creates multiple resource instances by iterating over a list, applicalbe to List of strings, and Uses zero-based index $count.index to access list elements. Not suitable for sets or maps.
3. for_each Iterates over sets or maps, provisioning one resource per element, applicable to both Set or map of strings, and Access items via $each.key and $each.value. Appropriate for collections without indexes.

Below is the video guide on how Terraform Meta Arguments work