Task 3.4: Import existing infrastructure to an infrastructure project

• AA script that runs terraform import once per bucket with the module address and bucket ID

  Incorrect

  terraform import changes state one object at a time outside the plan, so the forty imports are never reviewed together in one plan.

• BAn import block with to = module.team.aws_s3_bucket.this and id = local.inventory[*].bucket_id

  Incorrect

  to must name one instance address and id must be a single string, so the module and resource keys cannot be left out.

• COne import block with for_each = local.inventory, id = each.value.bucket_id and to = module.team[each.value.team].aws_s3_bucket.this[each.value.name]

  Correct

  An import block's for_each can loop over a list of objects, and the to address can use each.value for both the module key and the resource key.

• DImport blocks inside ./team-buckets with for_each = local.inventory, one module per team

  Incorrect

  local.inventory is defined in the root module, and local values are available only in the module that defines them, so the shared module cannot iterate over it.

for_each in import blocks lets one block import many objects into module instances and resource instances alike, all visible in a single plan before anything is written to state.

• AImport blocks accept only literal strings

  Incorrect

  The id can be an expression, such as a variable, if it evaluates to a string.

• BImport blocks must sit in a separate imports.tf file

  Incorrect

  Import blocks can be in any configuration file.

• CThe ID must be known during the plan operation

  Correct

  The id must evaluate to a string that is known at plan time, and an attribute of a resource created in the same run is unknown then.

• DOnly terraform import can use a resource attribute

  Incorrect

  The CLI command takes a literal ID on the command line.

Pass known IDs through variables or data sources whose values are available while planning.

• Aregion = "us-east-1" inside the import block

  Incorrect

  Import blocks have no region argument.

• Balias = "east" inside the import block

  Incorrect

  alias belongs in provider blocks.

• Cfor_each over the provider configurations

  Incorrect

  for_each repeats the import; it does not choose a provider.

• Dprovider = aws.east

  Correct

  The provider meta-argument tells Terraform which provider configuration to import the resource with.

The resource block for the imported object should name the same provider configuration.

• Agenerated.tf already exists, and the command will not overwrite it

  Correct

  Rerunning the command when the file already exists at that path results in an error, so remove the file before each run.

• BIn HCP Terraform workspaces the file is written remotely instead

  Incorrect

  Even when connected to HCP Terraform, the command writes generated.tf on the local workstation.

• CThe flag works only once per directory until terraform init runs again

  Incorrect

  No such limit exists; the existing file is the problem.

• DGenerated configuration needs a name ending in .tfquery.hcl

  Incorrect

  .tfquery.hcl is for query files; the generated configuration is an ordinary .tf file.

The generated file holds resource and import blocks, including resource identities. Copy what you need into the configuration, then delete the file before the next run.

• Aterraform import ignores configuration files and needs flags

  Incorrect

  Terraform loads configuration files that configure the provider.

• BThe provider configuration cannot depend on non-variable inputs

  Correct

  For import, provider configuration may use variables but must not depend on inputs such as a data source.

• CThe command works only with the local backend

  Incorrect

  import works with remote backends too.

• DProvider blocks must be removed before importing

  Incorrect

  The command uses provider blocks when they are present.

Pass the region through a variable for the import, or use an import block, which plans with the full configuration.