Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
13 KiB
Refusing a VPC Peering Connection
Function
After tenant A requests to create a VPC peering connection with a VPC of tenant B, the VPC peering connection takes effect only after tenant B accepts the request. However, tenant can refuse the VPC peering connection request. This API is used by a tenant to refuse a VPC peering connection request initiated by another tenant.
Request Parameters
None
Example Request
- Reject the VPC peering connection request from 22b76469-08e3-4937-8c1d-7aad34892be1.
PUT https://{Endpoint}/v2.0/vpc/peerings/22b76469-08e3-4937-8c1d-7aad34892be1/reject
Response Parameters
Attribute |
Type |
Description |
---|---|---|
id |
String |
Specifies the VPC peering connection ID. |
name |
String |
Specifies the VPC peering connection name. |
status |
String |
Specifies the VPC peering connection status. Possible values are as follows:
|
request_vpc_info |
vpc_info object |
Specifies information about the local VPC. For details, see Table 3. |
accept_vpc_info |
vpc_info object |
Specifies information about the peer VPC. For details, see Table 3. |
description |
String |
Provides supplementary information about the VPC peering connection. |
created_at |
String |
Specifies the time (UTC) when the VPC peering connection is created. Format: yyyy-MM-ddTHH:mm:ss |
updated_at |
String |
Specifies the time (UTC) when the VPC peering connection is updated. Format: yyyy-MM-ddTHH:mm:ss |
Example Response
{ "name": "test", "id": "22b76469-08e3-4937-8c1d-7aad34892be1", "request_vpc_info": { "vpc_id": "9daeac7c-a98f-430f-8e38-67f9c044e299", "tenant_id": "f65e9ebc-ed5d-418b-a931-9a723718ba4e" }, "accept_vpc_info": { "vpc_id": "f583c072-0bb8-4e19-afb2-afb7c1693be5", "tenant_id": "f65e9ebc-ed5d-418b-a931-9a723718ba4e" }, "status": "REJECTED" }
Status Code
See Status Codes.
Error Code
See Error Codes.