使用 Terraform 导入 Azure 上的现有资源 [英] Using Terraform to import existing resources on Azure

查看:25
本文介绍了使用 Terraform 导入 Azure 上的现有资源的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在 Azure 上有一个现有的资源组,上面运行着一个 VM,并且一直在使用 Terraform 尝试将资源导入我的状态文件.

I have an existing resource group on Azure with a VM running on it and have been playing around with Terraform to try and import the resource to my state file.

我已经设置了一个骨架文件,据我所知,一旦我导入 TF 就应该用 Azure 中我的资源组上的值填充它

I have set up a skeleton file, and as far as my understanding is once I import TF should populate this with the values on my resource group in Azure

resource "azurerm" "example" {
# ...instance configuration...
  name = "MyResourceGroup"

}

我从 CLI 运行的命令:

Command I am running from CLI:

terraform import azurerm_resource_group.MyResourceGroup/subscriptions/MySubscriptionNumber/resourceGroups/MyResourceGroup

来自 Terraform 的消息:

Message from Terraform:

The import command expects two arguments.
Usage: terraform import [options] ADDR ID

  Import existing infrastructure into your Terraform state.

  This will find and import the specified resource into your Terraform
  state, allowing existing infrastructure to come under Terraform
  management without having to be initially created by Terraform.

  The ADDR specified is the address to import the resource to. Please
  see the documentation online for resource addresses. The ID is a
  resource-specific ID to identify that resource being imported. Please
  reference the documentation for the resource type you're importing to
  determine the ID syntax to use. It typically matches directly to the ID
  that the provider uses.

  The current implementation of Terraform import can only import resources
  into the 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
  a resource configuration block for the resource manually, to which the
  imported object will be attached.

  This command will not modify your infrastructure, but it will make
  network requests to inspect parts of your infrastructure relevant to
  the resource being imported.

Options:

  -backup=path            Path to backup the existing state file before
                          modifying. Defaults to the "-state-out" path with
                          ".backup" extension. Set to "-" to disable backup.

  -config=path            Path to a directory of Terraform configuration files
                          to use to configure the provider. Defaults to pwd.
                          If no config files are present, they must be provided
                          via the input prompts or env vars.

  -allow-missing-config   Allow import when no resource configuration block exists.

  -input=true             Ask for input for variables if not directly set.

  -lock=true              Lock the state file when locking is supported.

  -lock-timeout=0s        Duration to retry a state lock.

  -no-color               If specified, output won't contain any color.

  -provider=provider      Specific provider to use for import. This is used for
                          specifying aliases, such as "aws.eu". Defaults to the
                          normal provider prefix of the resource being imported.

  -state=PATH             Path to the source state file. Defaults to the configured
                          backend, or "terraform.tfstate"

  -state-out=PATH         Path to the destination state file to write to. If this
                          isn't specified, the source state file will be used. This
                          can be a new or existing path.

  -var 'foo=bar'          Set a variable in the Terraform configuration. This
                          flag can be set multiple times. This is only useful
                          with the "-config" flag.

  -var-file=foo           Set variables in the Terraform configuration from
                          a file. If "terraform.tfvars" or any ".auto.tfvars"
                          files are present, they will be automatically loaded.

非常感谢任何帮助

推荐答案

看来您需要先修复脚本文件 - azurerm 不是有效的资源名称,您的意思是:

It looks like you need to fix your script file first - azurerm isn't a valid resource name, did you mean:

resource "azurerm_resource_group" "example" {
    # ...instance configuration...
    name = "MyResourceGroup"    
}

<小时>

如输出所示,import 需要两个参数,ADDRID - 你只是通过(我假设是) 身份证.您还需要告诉 terraform 它映射到脚本中的哪个资源:


As seen in the output, import is expecting two parameters, ADDR and ID - you're only passing (what I assume is) the ID. You also need to tell terraform which resource in your script it maps to:

terraform import azurerm_resource_group.example 
  /subscriptions/MySubscriptionNumber/resourceGroups/MyResourceGroup

这篇关于使用 Terraform 导入 Azure 上的现有资源的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆