terraform-provider-stackitp.../docs/data-sources/routing_table_route.md
Ruben Hönle 9ff9b8f610
feat(iaas): add experimental support for routing tables and routes (#896)
* Merged PR 788126: feat(iaas): Onboard routing tables

feat(iaas): Onboard routing tables

Signed-off-by: Alexander Dahmen <alexander.dahmen@inovex.de>

* Merged PR 793350: fix(routingtable): region attribute is missing in scheme

fix(routingtable): region attribute is missing in scheme

Signed-off-by: Alexander Dahmen <alexander.dahmen@inovex.de>

* Merged PR 797968: feat(iaas): onboarding of routing table routes

relates to STACKITTPR-241

* use iaasalpha sdk from github

* resolve todos

* remove routes from routing table model

* restructure packages

* acc tests routing tables

* add acc tests for routes

* chore(iaas): mark routing table resources as experimental

* chore(deps): use iaasalpha sdk v0.1.19-alpha

* Review feedback

Signed-off-by: Alexander Dahmen <alexander.dahmen@inovex.de>

---------

Signed-off-by: Alexander Dahmen <alexander.dahmen@inovex.de>
Co-authored-by: Alexander Dahmen (EXT) <Alexander.Dahmen_ext@external.mail.schwarz>
Co-authored-by: Alexander Dahmen <alexander.dahmen@inovex.de>
2025-07-02 10:30:50 +02:00

2.7 KiB

page_title subcategory description
stackit_routing_table_route Data Source - stackit Routing table route datasource schema. Must have a region specified in the provider configuration. ~> This datasource is part of the routing-tables experiment and is likely going to undergo significant changes or be removed in the future. Use it at your own discretion.

stackit_routing_table_route (Data Source)

Routing table route datasource schema. Must have a region specified in the provider configuration.

~> This datasource is part of the routing-tables experiment and is likely going to undergo significant changes or be removed in the future. Use it at your own discretion.

Example Usage

data "stackit_routing_table_route" "example" {
  organization_id  = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  network_area_id  = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  routing_table_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  route_id         = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Schema

Required

  • network_area_id (String) The network area ID to which the routing table is associated.
  • organization_id (String) STACKIT organization ID to which the routing table is associated.
  • route_id (String) Route ID.
  • routing_table_id (String) The routing tables ID.

Optional

  • region (String) The resource region. If not defined, the provider region is used.

Read-Only

  • created_at (String) Date-time when the route was created
  • destination (Attributes) Destination of the route. (see below for nested schema)
  • id (String) Terraform's internal datasource ID. It is structured as "organization_id,region,network_area_id,routing_table_id,route_id".
  • labels (Map of String) Labels are key-value string pairs which can be attached to a resource container
  • next_hop (Attributes) Next hop destination. (see below for nested schema)
  • updated_at (String) Date-time when the route was updated

Nested Schema for destination

Read-Only:

  • type (String) CIDRV type. Possible values are: cidrv4, cidrv6. Only cidrv4 is supported during experimental stage.
  • value (String) An CIDR string.

Nested Schema for next_hop

Read-Only:

  • type (String) Possible values are: blackhole, internet, ipv4, ipv6. Only cidrv4 is supported during experimental stage..
  • value (String) Either IPv4 or IPv6 (not set for blackhole and internet). Only IPv4 supported during experimental stage.