Disassociating a VPC from an Endpoint Rule_Resolver Management_APIs_API Reference (Ally Region)

Function

This API is used to disassociate a VPC from an endpoint rule.

URI

POST /v2.1/resolverrules/{resolverrule_id}/disassociaterouter

**Table 1** Path parameter
Parameter	Mandatory	Type	Description
resolverrule_id	Yes	String	ID of an endpoint rule

Request Parameters

**Table 2** Request header parameter
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token. The token can be obtained by calling an IAM API. The value of X-Subject-Token in the response header is the user token.

**Table 3** Request body parameter
Parameter	Mandatory	Type	Description
router	Yes	RouterForRule object	VPC

**Table 4** RouterForRule
Parameter	Mandatory	Type	Description
router_id	Yes	String	ID of the Router (VPC) associated with the zone

Response Parameters

Status code: 202

**Table 5** Response body parameters
Parameter	Type	Description
router_id	String	ID of the associated VPC
router_region	String	Region where the associated VPC is located
status	String	Resource status

Example Requests

Disassociating a VPC from an endpoint rule

POST https://{endpoint}/v2.1/resolverrules/{resolverrule_id}/disassociaterouter

{
  "router" : {
    "router_id" : "f0791650-db8c-4a20-8a44-a06c6e24b15b"
  }
}

Example Responses

Status code: 202

Request accepted

{
  "status" : "PENDING_DELETE",
  "router_id" : "f0791650-db8c-4a20-8a44-a06c6e24b15b",
  "router_region" : "xx"
}

Status Codes

Status Code	Description
202	Request accepted

Error Codes

For details, see Error Codes.

Disassociating a VPC from an Endpoint Rule