opentelekomcloud_er_route_tables_v3¶
Use this data source to query the route tables under the ER instance within OpenTelekomCloud.
Example Usage¶
Querying specified route tables under ER instance using name¶
variable "instance_id" {}
variable "route_table_name" {}
data "opentelekomcloud_er_route_tables_v3" "test" {
instance_id = var.instance_id
name = var.route_table_name
}
Argument Reference¶
The following arguments are supported:
instance_id- (Required, String) Specifies the ID of the ER instance to which the route tables belongs.route_table_id- (Optional, String) Specifies the route table ID used to query specified route table.name- (Optional, String) Specifies the name used to filter the route tables. The name can contain1to64characters, only English letters, digits, underscore (_), hyphens (-) and dots (.) allowed.tags- (Optional, Map) Specifies the key/value pairs used to filter the route tables.
Attribute Reference¶
In addition to all arguments above, the following attributes are exported:
id- The data source ID.route_tables- All route tables that match the filter parameters. The object structure is documented below.
The route_tables block supports:
id- The route table ID.name- The name of the route table.description- The description of the route table.associations- The association configurations of the route table. The object structure is documented below.propagations- The propagation configurations of the route table. The object structure is documented below.routes- The route details of the route table. The object structure is documented below.created_at- The creation time.updated_at- The latest update time.
The associations or propagations block supports:
id- The ID of the association/propagation.attachment_id- The attachment ID corresponding to the routing association/propagation.attachment_type- The attachment type corresponding to the routing association/propagation.
id- The route ID.destination- The destination address (CIDR) of the route.is_blackhole- Whether route is the black hole route.attachments- The details of the attachment corresponding to the route. The object structure is documented below.
The attachments block supports:
attachment_id- The ID of the nexthop attachment.attachment_type- The type of the nexthop attachment.resource_id- The ID of the resource associated with the attachment.