mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-05-27 07:03:11 -04:00
b54017ef83
Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Co-authored-by: Kevin Wang <kwangsan@gmail.com> Co-authored-by: Judith Malnick <judith@hashicorp.com> Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: HashiBot <62622282+hashibot-web@users.noreply.github.com>
44 lines
2.2 KiB
Plaintext
44 lines
2.2 KiB
Plaintext
---
|
|
page_title: Import
|
|
description: >-
|
|
Terraform can import and manage existing infrastructure. This can help you
|
|
transition your infrastructure to Terraform.
|
|
---
|
|
|
|
# Import
|
|
|
|
> **Hands-on:** Try the [Import Terraform Configuration](https://learn.hashicorp.com/tutorials/terraform/state-import?in=terraform/state&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorial.
|
|
|
|
Terraform can import existing infrastructure resources. This functionality allows you take
|
|
resources you created by some other means and bring them under Terraform
|
|
management.
|
|
|
|
This is a great way to slowly transition infrastructure to Terraform, or
|
|
to be able to be confident that you can use Terraform in the future if it
|
|
potentially doesn't support every feature you need today.
|
|
|
|
~> Warning: Terraform expects that each remote object it is managing will be
|
|
bound to only one resource address, which is normally guaranteed by Terraform
|
|
itself having created all objects. If you import existing objects into Terraform,
|
|
be careful to import each remote object to only one Terraform resource address.
|
|
If you import the same object multiple times, Terraform may exhibit unwanted
|
|
behavior. For more information on this assumption, see
|
|
[the State section](/language/state).
|
|
|
|
## Currently State Only
|
|
|
|
The current implementation of Terraform import can only import resources
|
|
into the [state](/language/state). It does not generate configuration. A future
|
|
version of Terraform will also generate configuration.
|
|
|
|
Because of this, prior to running `terraform import` it is necessary to write
|
|
manually a `resource` configuration block for the resource, to which the
|
|
imported object will be mapped.
|
|
|
|
While this may seem tedious, it still gives Terraform users an avenue for
|
|
importing existing resources.
|
|
|
|
## Terraform Cloud
|
|
|
|
When you use Terraform on the command line with Terraform Cloud, many commands (e.g., `apply`) run inside your Terraform Cloud environment. However, the `import` command runs locally, so it will not have access to information from Terraform Cloud. To successfully perform an import, you may need to set local variables equivalent to any remote workspace variables in Terraform Cloud.
|