terraform-provider-binarylane/docs/resources/vpc_route_entries.md

page_title, subcategory, description

page_title	subcategory	description
binarylane_vpc_route_entries Resource - terraform-provider-binarylane

binarylane_vpc_route_entries (Resource)

Example Usage

resource "binarylane_vpc" "example" {
  name     = "tf-example-vpc"
  ip_range = "10.240.0.0/16"
}

resource "binarylane_server" "web" {
  # ...
  vpc_id = binarylane_vpc.example.id
}

resource "binarylane_vpc_route_entries" "example" {
  vpc_id = binarylane_vpc.example.id
  route_entries = [
    {
      description = "NAT"
      destination = "0.0.0.0/0"
      router      = binarylane_server.web.private_ipv4_addresses.0
    },
    {
      description = "VPN"
      destination = "192.168.1.0/24"
      router      = binarylane_server.vpn.private_ipv4_addresses.0
    }
  ]
}

Schema

Required

• vpc_id (Number) The target vpc id.

Optional

• route_entries (Attributes List) Submit null to leave unaltered, submit an empty list to clear all route entries. It is not possible to PATCH individual route entries, to alter a route entry submit the entire list of route entries you wish to save. (see below for nested schema)

Nested Schema for route_entries

Required:

• destination (String) The destination address for this route entry. This may be in CIDR format.
• router (String) The server that will receive traffic sent to the destination property in this VPC.

Optional:

• description (String) An optional description for the route.

Import

Import is supported using the following syntax:

terraform import binarylane_vpc_route_entries.example "<vpc_id>"