Question

A developer is calling a reusable VPC module and wants to create three copies of it. They add `count = 3` to the module block, but they also expect the child module to automatically receive a variable named `count` that it can reference internally. When they run `terraform plan`, the child module cannot find any variable called `count`. What is the correct explanation of this behavior?

Accepted Answer

`count` is a meta-argument handled by Terraform itself and is not passed into the child module as an input variable; the module can use `count.index` only in its own resources if it declares its own count logic.

Answer

Meta-arguments like `count` are automatically exposed to child modules as input variables of the same name, so the child module must simply declare a matching variable block.

Answer

The child module must add `count` to its `outputs.tf` file to make the value visible during planning.

Answer

Terraform only supports `for_each` on module blocks, so the `count` meta-argument is silently ignored and never affects the child module.