deleteVpcPeeringInstance
- Print
- PDF
deleteVpcPeeringInstance
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Can be used in a VPC environment.
Overview
Delete the VPC Peering instance.
Request
Request parameter
| Parameter Name | Required Status | Type | Restrictions | Description |
|---|---|---|---|---|
| regionCode | No | String | Region Code You can decide the region of the VPC Peering instance to be deleted. The regionCode can be obtained through the getRegionList action. Default: Select the first region of the getRegionList query results. | |
| vpcPeeringInstanceNo | Yes | String | The number of the VPC Peering instance to be deleted vpcPeeringInstanceNo can be obtained through the getVpcPeeringInstanceList action. | |
| responseFormatType | No | String | Format type for the response result Options : xml | json Default : xml |
Response
Response data type
- VpcPeeringInstanceList type
| VpcPeeringInstanceList extends CommonResponse |
|---|
| private Integer totalRows; |
| private List |
| VpcPeeringInstance |
|---|
| private String vpcPeeringInstanceNo; |
| private String vpcPeeringName; |
| private String regionCode; |
| private Date createDate; |
| private Date lastModifyDate; |
| private CommonCode vpcPeeringInstanceStatus; |
| private String vpcPeeringInstanceStatusName; |
| private CommonCode vpcPeeringInstanceOperation; |
| private String sourceVpcNo; |
| private String sourceVpcName; |
| private String sourceVpcIpv4CidrBlock; |
| private String sourceVpcLoginId; |
| private String targetVpcNo; |
| private String targetVpcName; |
| private String targetVpcIpv4CidrBlock; |
| private String targetVpcLoginId; |
| private String vpcPeeringDescription; |
| private Boolean hasReverseVpcPeering; |
| private Boolean isBetweenAccounts; |
| private String reverseVpcPeeringInstanceNo; |
Example
Request example
ncloud vpc deleteVpcPeeringInstance --regionCode KR --vpcPeeringInstanceNo ***6212
Response example
<deleteVpcPeeringInstanceResponse>
<requestId>5330ebe7-150b-40a3-8b6d-2cac0863ea91</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<vpcPeeringInstanceList>
<vpcPeeringInstance>
<vpcPeeringInstanceNo>***6212</vpcPeeringInstanceNo>
<vpcPeeringName>test-***</vpcPeeringName>
<regionCode>KR</regionCode>
<createDate>2020-08-07T17:53:06+0900</createDate>
<vpcPeeringInstanceStatus>
<code>RUN</code>
<codeName>run</codeName>
</vpcPeeringInstanceStatus>
<vpcPeeringInstanceStatusName>Deleting</vpcPeeringInstanceStatusName>
<vpcPeeringInstanceOperation>
<code>TERMT</code>
<codeName>TERMINATE OP</codeName>
</vpcPeeringInstanceOperation>
<sourceVpcNo>***05</sourceVpcNo>
<sourceVpcName>test-***</sourceVpcName>
<sourceVpcIpv4CidrBlock>***.**1.0.0/16</sourceVpcIpv4CidrBlock>
<sourceVpcLoginId>test-***@naver.com</sourceVpcLoginId>
<targetVpcNo>***06</targetVpcNo>
<targetVpcName>test-***</targetVpcName>
<targetVpcIpv4CidrBlock>***.**2.0.0/16</targetVpcIpv4CidrBlock>
<targetVpcLoginId>test-***@naver.com</targetVpcLoginId>
<vpcPeeringDescription></vpcPeeringDescription>
<hasReverseVpcPeering>false</hasReverseVpcPeering>
<isBetweenAccounts>false</isBetweenAccounts>
<reverseVpcPeeringInstanceNo></reverseVpcPeeringInstanceNo>
</vpcPeeringInstance>
</vpcPeeringInstanceList>
</deleteVpcPeeringInstanceResponse>
Was this article helpful?