Help Center/ Enterprise Router/ API Reference/ APIs/ Propagations/ Creating a Route Propagation
Updated on 2024-04-25 GMT+08:00

Creating a Route Propagation

Function

This API is used to create a route propagation. A propagation can be created for each attachment to propagate routes to one or more route tables on an enterprise router.

Calling Method

For details, see Calling APIs.

URI

POST /v3/{project_id}/enterprise-router/{er_id}/route-tables/{route_table_id}/enable-propagations

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID

er_id

Yes

String

Enterprise router ID

route_table_id

Yes

String

Route table ID

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Client-Token

No

String

Idempotence identifier

Minimum: 1

Maximum: 64

Table 3 Request body parameters

Parameter

Mandatory

Type

Description

attachment_id

No

String

Unique ID of the attachment

Response Parameters

Status code: 202

Table 4 Response header parameters

Parameter

Type

Description

X-Client-Token

-

Idempotence identifier

Table 5 Response body parameters

Parameter

Type

Description

propagation

Propagation object

Propagation details

request_id

String

Request ID

Table 6 Propagation

Parameter

Type

Description

id

String

Unique association ID

project_id

String

Project ID

er_id

String

Enterprise router ID

route_table_id

String

Unique ID of the route table

attachment_id

String

Unique ID of the attachment

resource_type

String

Attachment type.

  • vpc: VPC attachment

  • vpn: VPN gateway attachment

  • vgw: virtual gateway attachment

resource_id

String

Unique ID of the attachment

state

String

Status. Value options: pending, available, modifying, deleting, deleted, and failed

created_at

String

Creation time. It is UTC time in the format of YYYY-MM-DDTHH:MM:SS.

updated_at

String

Update time. It is UTC time in the format of YYYY-MM-DDTHH:MM:SS.

Example Requests

Creating a route propagation

POST https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/ad838a5e-dbef-22cc-b1d9-cb46bef77ae8/route-tables/915a14a6-867b-4af7-83d1-70efceb146f9/enable-propagations

{
  "attachment_id" : "a5b7d209-dc02-4c46-a51f-805eadd3de64"
}

Example Responses

Status code: 202

Accepted

{
  "propagation" : {
    "id" : "915a14a6-867b-4af7-83d1-70efceb146f9",
    "route_table_id" : "91c013e2-d65a-474e-9177-c3e1799ca726",
    "attachment_id" : "a5b7d209-dc02-4c46-a51f-805eadd3de64",
    "resource_type" : "vpc",
    "resource_id" : "4e5fe97c-82bc-432e-87d8-06d7e157dffa",
    "route_policy" : {
      "import_policy_id" : ""
    },
    "state" : "pending",
    "created_at" : "2020-03-11T15:13:31Z",
    "updated_at" : "2020-03-11T15:13:31Z"
  },
  "request_id" : "915a14a6-867b-4af7-83d1-70efceb146f9"
}

Status Codes

Status Code

Description

202

Accepted

Error Codes

See Error Codes.