Import block syntax (Terraform 1.5+) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the import block in Terraform 1.5+?

The import block lets you bring existing infrastructure resources into Terraform's management by specifying their IDs directly in the configuration.

beginner

How do you specify the resource to import using the new import block syntax?

You specify the resource address and the ID of the existing resource inside the <code>import</code> block, like this:<br><pre>import {
  to = aws_instance.example
  id = "i-1234567890abcdef0"
}</pre>

intermediate

Can you use multiple import blocks in a single Terraform configuration?

Yes, you can use multiple <code>import</code> blocks to import several resources at once, each with its own <code>to</code> and <code>id</code> values.

intermediate

What happens if you try to import a resource that is already managed by Terraform?

Terraform will show an error because the resource is already tracked in the state. You should only import resources not yet managed.

advanced

Why is the import block syntax preferred over the old CLI import command?

The import block syntax allows you to declare imports as part of your configuration files, making imports repeatable, version-controlled, and easier to automate.

What key fields must an import block contain in Terraform 1.5+?

A <code>address</code> and <code>type</code>

B <code>resource</code> and <code>name</code>

C <code>source</code> and <code>destination</code>

D <code>to</code> and <code>id</code>

The import block requires to (resource address) and id (existing resource ID) fields.

Can the import block be used to create new resources in Terraform?

A No, it only imports existing resources

B Yes, it creates new resources automatically

C Yes, but only for AWS resources

D No, it deletes existing resources

The import block only brings existing resources under Terraform management; it does not create new resources.

Which Terraform version introduced the import block syntax?

A Terraform 0.12

B Terraform 1.0

C Terraform 1.5

D Terraform 2.0

Terraform 1.5 introduced the import block syntax to declare imports in configuration files.

What is the benefit of declaring imports in Terraform configuration files?

A Imports become part of version control and automation

B Imports run faster

C Imports require no resource IDs

D Imports automatically update resource code

Declaring imports in config files makes them repeatable, version-controlled, and easier to automate.

If you want to import multiple resources, what should you do?

A Use one import block with multiple IDs

B Use multiple import blocks, one per resource

C Import only one resource at a time

D Use the CLI import command instead

You use multiple import blocks, each specifying one resource to import.

Explain how the import block syntax works in Terraform 1.5+ and why it is useful.

Think about how Terraform manages resources and why importing is needed.

Describe the steps to import an existing AWS instance using the import block syntax.

Focus on the syntax and the process flow.