能否将Azure中的资源组、虚拟网络或子网声明为Terraform变量？

Absolutely! You can definitely use Terraform variables to work with Azure resource groups, virtual networks (VNets), and subnets—how you implement this depends on whether you're referencing existing resources or configuring parameters for new resources you're creating. Let's break down both scenarios with practical examples:

1. Referencing Existing Azure Resources #

If you need to work with resources that already exist in your Azure environment, you can declare their identifiers (like names or IDs) as variables, then use Terraform's data sources to fetch their details for use in your configuration.

Step 1: Define Variables for Existing Resources #

variable "existing_resource_group_name" {
  type        = string
  description = "Name of the pre-existing resource group we need to reference"
}

variable "existing_vnet_name" {
  type        = string
  description = "Name of the existing virtual network in the resource group"
}

variable "existing_subnet_name" {
  type        = string
  description = "Name of the subnet within the existing VNet"
}

Step 2: Fetch Resource Details with Data Sources #

# Get details of the existing resource group
data "azurerm_resource_group" "existing" {
  name = var.existing_resource_group_name
}

# Get details of the existing VNet
data "azurerm_virtual_network" "existing" {
  name                = var.existing_vnet_name
  resource_group_name = data.azurerm_resource_group.existing.name
}

# Get details of the existing subnet
data "azurerm_subnet" "existing" {
  name                 = var.existing_subnet_name
  virtual_network_name = data.azurerm_virtual_network.existing.name
  resource_group_name  = data.azurerm_resource_group.existing.name
}

Step 3: Use the Referenced Resources #

You can now use these fetched resources in other Terraform blocks. For example, attaching a network interface to the existing subnet:

resource "azurerm_network_interface" "example" {
  name                = "example-nic"
  location            = data.azurerm_resource_group.existing.location
  resource_group_name = data.azurerm_resource_group.existing.name

  ip_configuration {
    name                          = "internal"
    subnet_id                     = data.azurerm_subnet.existing.id
    private_ip_address_allocation = "Dynamic"
  }
}

2. Using Variables to Configure New Resources #

If you're creating new resource groups, VNets, or subnets, variables let you parameterize their properties (like names, address spaces, or locations) to make your configuration reusable across environments.

Step 1: Define Variables for New Resource Parameters #

variable "resource_group_name" {
  type        = string
  description = "Name for the new resource group"
  default     = "example-rg" # Optional default value; users can override this
}

variable "vnet_address_space" {
  type        = list(string)
  description = "CIDR address space for the new virtual network"
  default     = ["10.0.0.0/16"]
}

variable "subnet_address_prefixes" {
  type        = list(string)
  description = "CIDR prefixes for subnets to create in the VNet"
  default     = ["10.0.1.0/24", "10.0.2.0/24"]
}

variable "location" {
  type        = string
  description = "Azure region for all resources"
  default     = "eastus"
}

Step 2: Create Resources Using Variables #

# Create the new resource group
resource "azurerm_resource_group" "example" {
  name     = var.resource_group_name
  location = var.location
}

# Create the new VNet
resource "azurerm_virtual_network" "example" {
  name                = "example-vnet"
  address_space       = var.vnet_address_space
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
}

# Create multiple subnets using the variable list (via count)
resource "azurerm_subnet" "example" {
  count                = length(var.subnet_address_prefixes)
  name                 = "example-subnet-${count.index + 1}"
  resource_group_name  = azurerm_resource_group.example.name
  virtual_network_name = azurerm_virtual_network.example.name
  address_prefixes     = [var.subnet_address_prefixes[count.index]]
}

Bonus: Passing Entire Resource Objects as Variables (For Modules) #

If you're using Terraform modules, you can even pass entire resource objects as variables (using the object type) to make modules more flexible. For example, a module might accept a resource group object instead of individual name/location variables:

Module Variable Definition #

variable "resource_group" {
  type = object({
    name     = string
    location = string
    id       = string
  })
  description = "The resource group object to use for all resources in this module"
}

Calling the Module #

module "web_app" {
  source = "./modules/web-app"
  resource_group = azurerm_resource_group.example # Pass the entire resource group object
}

内容的提问来源于stack exchange，提问作者SamJack