Bulk import strategies in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of bulk import strategies in Terraform?

Bulk import strategies help bring many existing cloud resources under Terraform management efficiently, saving time and reducing manual work.

intermediate

How does the 'terraform import' command work in bulk import scenarios?

The 'terraform import' command links an existing resource to a Terraform resource block, but it works one resource at a time, so scripts or loops are used to import many resources.

beginner

Why is scripting important in bulk import strategies?

Scripting automates repetitive import commands, making it faster and less error-prone to import many resources at once.

intermediate

What is a common challenge when performing bulk imports in Terraform?

Ensuring the Terraform configuration matches the existing resources exactly to avoid drift or errors after import.

beginner

Name one best practice for bulk importing resources into Terraform.

Test imports on a small set of resources first, verify the state, then scale up to bulk import to avoid mistakes.

What does the 'terraform import' command do?

A Deletes resources from Terraform state

B Creates new resources in the cloud

C Updates Terraform configuration files automatically

D Links existing resources to Terraform state

'terraform import' connects existing cloud resources to Terraform's state without creating or deleting them.

Which method helps automate bulk imports in Terraform?

A Writing scripts to run multiple import commands

B Manually running import for each resource

C Using 'terraform apply' directly

D Deleting resources before import

Scripts automate running many 'terraform import' commands, making bulk import efficient.

Why should you verify Terraform configuration before bulk import?

A To speed up the import process

B To ensure resource definitions match existing resources

C To delete unused resources automatically

D To create new resources instead

Matching configuration prevents errors and drift after import.

What is a risk of bulk importing without testing first?

A Importing wrong resources or corrupting state

B Terraform will create duplicate resources

C Cloud provider will charge extra fees

D Terraform will ignore imported resources

Testing helps avoid mistakes that can corrupt Terraform state or import wrong resources.

Which of these is NOT a bulk import strategy?

A Using scripts to automate imports

B Manual import one by one

C Using Terraform Cloud to import automatically

D Writing configuration to match existing resources

Terraform Cloud does not provide automatic bulk import; automation is done via scripts and configuration.

Explain how you would perform a bulk import of cloud resources into Terraform.

Think about commands, automation, configuration, and testing.

What are the key challenges and best practices when doing bulk imports in Terraform?

Consider risks and how to prevent them.

Practice

1. What is the main purpose of using bulk import strategies in Terraform?

easy

A. To automatically generate Terraform code for new resources

B. To create new resources faster than usual

C. To delete multiple resources simultaneously

D. To efficiently bring many existing resources under Terraform management at once

Solution

1. Step 1: Understand Terraform import

   Terraform import lets you bring existing cloud resources into Terraform state so you can manage them.

2. Step 2: Recognize bulk import purpose

   Bulk import strategies help import many resources quickly instead of one by one.

3. Final Answer:

   To efficiently bring many existing resources under Terraform management at once -> Option D

4. Quick Check:

   Bulk import = manage many existing resources [OK]

Hint: Bulk import means importing many existing resources at once [OK]

Common Mistakes:

• Thinking bulk import creates new resources
• Confusing import with resource deletion
• Assuming import auto-generates Terraform code

2. Which Terraform command is used to import a resource into the state file?

easy

A. terraform import

B. terraform plan

C. terraform init

D. terraform apply

Solution

1. Step 1: Recall Terraform commands

   terraform apply creates or updates resources, terraform init initializes, terraform plan previews changes.

2. Step 2: Identify import command

   terraform import is the command that brings existing resources into Terraform state.

3. Final Answer:

   terraform import -> Option A

4. Quick Check:

   Import command = terraform import [OK]

Hint: Import existing resources with 'terraform import' command [OK]

Common Mistakes:

• Using terraform apply to import
• Confusing init with import
• Trying terraform plan to import

3. Given this script snippet to bulk import AWS EC2 instances:

for id in i-12345678 i-87654321; do terraform import aws_instance.example_$id $id; done

What will be the result after running this script?

medium

A. Terraform will create new instances instead of importing

B. Only the first instance will be imported, second will fail

C. Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321

D. The script will cause a syntax error and not run

Solution

1. Step 1: Analyze the for loop

   The loop iterates over two instance IDs: i-12345678 and i-87654321.

2. Step 2: Understand terraform import usage

   Each iteration runs terraform import with resource name aws_instance.example_$id and the ID as argument, importing both instances.

3. Final Answer:

   Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321 -> Option C

4. Quick Check:

   Loop imports both instances correctly [OK]

Hint: Loop imports each resource with unique name using ID [OK]

Common Mistakes:

• Assuming only one import runs
• Thinking terraform creates new instances
• Believing script syntax is invalid

4. You wrote a bulk import script but get errors: "Error: Resource name must not contain '-'". What is the likely cause?

medium

A. Using resource names with dashes (-) which Terraform disallows

B. Missing terraform init before import

C. Incorrect AWS credentials causing import failure

D. Trying to import resources that do not exist

Solution

1. Step 1: Understand Terraform resource naming rules

   Terraform resource names must use underscores (_) not dashes (-).

2. Step 2: Identify cause of error

   The error says resource name must not contain '-', so using dashes in resource names causes this error.

3. Final Answer:

   Using resource names with dashes (-) which Terraform disallows -> Option A

4. Quick Check:

   Resource names cannot have '-' [OK]

Hint: Use underscores (_) in resource names, not dashes (-) [OK]

Common Mistakes:

• Ignoring naming rules and using dashes
• Assuming missing init causes this error
• Blaming credentials for naming errors

5. You want to bulk import 100 existing Azure VMs into Terraform. Which approach best follows Terraform bulk import best practices?

hard

A. Run terraform import once with all VM IDs separated by commas

B. Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files

C. Manually import each VM one by one using terraform import command

D. Create new Terraform resources and delete existing VMs to sync state

Solution

1. Step 1: Understand bulk import best practice

   Bulk import works best with automation scripts looping over resource IDs to import each resource.

2. Step 2: Match Terraform configuration

   Terraform requires matching resource blocks in config files for imported resources to manage them properly.

3. Step 3: Evaluate options

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files uses scripting and matching config, Run terraform import once with all VM IDs separated by commas is invalid syntax, Manually import each VM one by one using terraform import command is slow manual work, Create new Terraform resources and delete existing VMs to sync state deletes resources which is unsafe.

4. Final Answer:

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files -> Option B

5. Quick Check:

   Automate import with matching config files [OK]

Hint: Automate imports with scripts and matching config files [OK]

Common Mistakes:

• Trying to import multiple IDs in one command
• Manually importing many resources without automation
• Deleting resources instead of importing