» alicloud_router_interfaces

This data source provides information about router interfaces that connect VPCs together.

» Example Usage

data "alicloud_router_interfaces" "router_interfaces_ds" {
  name_regex = "^testenv"
  status     = "Active"

output "first_router_interface_id" {
  value = "${data.alicloud_router_interfaces.router_interfaces_ds.interfaces.0.id}"

» Argument Reference

The following arguments are supported:

  • name_regex - (Optional) A regex string used to filter by router interface name.
  • status - (Optional) Expected status. Valid values are Active, Inactive and Idle.
  • specification - (Optional) Specification of the link, such as Small.1 (10Mb), Middle.1 (100Mb), Large.2 (2Gb), ...etc.
  • router_id - (Optional) ID of the VRouter located in the local region.
  • router_type - (Optional) Router type in the local region. Valid values are VRouter and VBR (physical connection).
  • role - (Optional) Role of the router interface. Valid values are InitiatingSide (connection initiator) and AcceptingSide (connection receiver). The value of this parameter must be InitiatingSide if the router_type is set to VBR.
  • opposite_interface_id - (Optional) ID of the peer router interface.
  • opposite_interface_owner_id - (Optional) Account ID of the owner of the peer router interface.
  • ids - (Optional, Available in 1.44.0+) A list of router interface IDs.
  • output_file - (Optional) File name where to save data source results (after running terraform plan).

» Attributes Reference

The following attributes are exported in addition to the arguments listed above:

  • ids - A list of router interface IDs.
  • names - A list of router interface names.
  • interfaces - A list of router interfaces. Each element contains the following attributes: