Terraform Import Existing Resources Language Collocations
Practise the standard verbs for importing existing resources into terraform state.
0 / 5 completed
1 / 5
Fill in: 'We ___ an existing manually-created resource into state before terraform is allowed to manage it going forward.'
We 'import a resource' — the standard, established terraform collocation for bringing an existing resource under management. The other options aren't the recognised term here.
2 / 5
Fill in: 'Importing a resource without a matching config block can ___ the very next plan proposing to destroy it.'
We say a mismatched import will 'leave' a resource proposed for destruction — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the generated plan carefully right after an import so terraform's view of the resource matches reality exactly.'
We 'review a plan' — the standard, simple collocation for checking a proposed set of changes. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a matching resource block before running the import command so terraform knows which config the state maps to.'
We 'write a block' — the standard, simple collocation for authoring a piece of terraform configuration. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ imports one resource at a time rather than in bulk so any mismatch is easy to isolate and fix.'
We 'run' an import — the standard, simple collocation for executing a single terraform command. The other options are less idiomatic here.