Gunakan DeleteTransitRouterVpcAttachment untuk menghapus koneksi VPC dari transit router - Cloud Enterprise Network - Alibaba Cloud - Cloud Enterprise Network

Menghapus koneksi virtual private cloud (VPC) dari Router transit Edisi Perusahaan.

Deskripsi operasi

DeleteTransitRouterVpcAttachment is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVpcAttachments operation to query the status of a VPC connection.

If a VPC connection is in the Detaching state, the VPC connection is being deleted. You can query the VPC connection but cannot perform other operations.
If a VPC connection cannot be found, it is deleted.

Prerequisites

Before you delete a VPC connection, make sure that the following requirements are met:

No associated forwarding correlation is established between the VPC connection and the route tables of the Enterprise Edition transit router. For more information about how to delete an associated forwarding correlation, see DissociateTransitRouterAttachmentFromRouteTable.
No route learning correlation is established between the VPC connection and the route tables of the Enterprise Edition transit router. For more information about how to delete a route learning correlation, see DisableTransitRouterRouteTablePropagation.
The route table of the VPC does not contain routes that point to the VPC connection. For more information about how to delete routes from a VPC route table, see DeleteRouteEntry.
The route tables of the Enterprise Edition transit router do not contain a custom route entry whose next hop is the network instance connection. For more information about how to delete custom routes from the route tables of an Enterprise Edition transit router, see DeleteTransitRouterRouteEntry.
The route tables of the Enterprise Edition transit router do not contain a route that is generated from a prefix list and the next hop is the VPC connection. You can delete such routes by disassociating the route table from the prefix list. For more information, see DeleteTransitRouterPrefixListAssociation.

Coba sekarang

Coba API ini di OpenAPI Explorer tanpa perlu penandatanganan manual. Panggilan yang berhasil akan secara otomatis menghasilkan contoh kode SDK sesuai dengan parameter Anda. Unduh kode tersebut dengan kredensial bawaan yang aman untuk penggunaan lokal.

Test

RAM authorization

Tabel berikut menjelaskan otorisasi yang diperlukan untuk memanggil API ini. Anda dapat menentukannya dalam kebijakan Resource Access Management (RAM). Kolom pada tabel dijelaskan sebagai berikut:

Action: Aksi yang dapat digunakan dalam elemen Action pada pernyataan kebijakan izin RAM untuk memberikan izin guna melakukan operasi tersebut.
API: API yang dapat Anda panggil untuk melakukan aksi tersebut.
Access level: Tingkat akses yang telah ditentukan untuk setiap API. Nilai yang valid: create, list, get, update, dan delete.
Resource type: Jenis resource yang mendukung otorisasi untuk melakukan aksi tersebut. Ini menunjukkan apakah aksi tersebut mendukung izin tingkat resource. Resource yang ditentukan harus kompatibel dengan aksi tersebut. Jika tidak, kebijakan tersebut tidak akan berlaku.
- Untuk API dengan izin tingkat resource, jenis resource yang diperlukan ditandai dengan tanda bintang (*). Tentukan Nama Sumber Daya Alibaba Cloud (ARN) yang sesuai dalam elemen Resource pada kebijakan.
- Untuk API tanpa izin tingkat resource, ditampilkan sebagai All Resources. Gunakan tanda bintang (*) dalam elemen Resource pada kebijakan.
Condition key: Kunci kondisi yang didefinisikan oleh layanan. Kunci ini memungkinkan kontrol granular, berlaku baik hanya untuk aksi maupun untuk aksi yang terkait dengan resource tertentu. Selain kunci kondisi spesifik layanan, Alibaba Cloud menyediakan serangkaian common condition keys yang berlaku di semua layanan yang didukung RAM.
Dependent action: Aksi dependen yang diperlukan untuk menjalankan aksi tersebut. Untuk menyelesaikan aksi tersebut, pengguna RAM atau role RAM harus memiliki izin untuk melakukan semua aksi dependen.

Action

Access level

Resource type

Condition key

Dependent action

cen:DeleteTransitRouterVpcAttachment

delete

*TransitRouterVpcAttachment

acs:cen:*:{#accountId}:centransitrouterattachment/{#centransitrouterattachmentId}

None

Parameter permintaan

Parameter	Type	Required	Description	Example
ClientToken	string	No	token klien yang digunakan untuk memastikan idempotensi permintaan. Anda dapat menggunakan Klien untuk menghasilkan token, tetapi Anda harus memastikan bahwa token tersebut unik di antara semua permintaan. token hanya dapat berisi karakter ASCII. Catatan Jika Anda tidak menetapkan parameter ini, ClientToken ditetapkan ke nilai RequestId. Nilai RequestId untuk setiap permintaan API dapat berbeda.	02fb3da4-130e-11e9-8e44-001****
TransitRouterAttachmentId	string	Yes	ID koneksi VPC.	tr-attach-ia340z7xis7t5s****
DryRun	boolean	No	Apakah akan menjalankan dry run. Nilai default: false (default): Menjalankan dry run dan mengirim permintaan. true: Menjalankan dry run. Sistem memeriksa parameter yang diperlukan dan sintaks permintaan. Jika permintaan gagal dalam dry run, Paket error dikembalikan. Jika permintaan lolos dry run, sistem mengembalikan ID permintaan.	false
Force	boolean	No	Apakah akan menghapus paksa koneksi VPC. Nilai valid: false (default): Memeriksa Sumber daya seperti korelasi penerusan terkait dan kebijakan pembelajaran entri rute yang terkait dengan koneksi VPC sebelum dihapus. Jika Sumber daya tersebut ada, koneksi VPC tidak dihapus dan Paket error dikembalikan. true: Menghapus koneksi VPC dan semua Sumber daya yang terkait dengan koneksi VPC.	false

Elemen respons

Element	Type	Description	Example
	object	The response.
RequestId	string	The ID of the request.	7E61D334-4025-41EF-9145-FC327B35301D

Contoh

Respons sukses

JSONformat

{
  "RequestId": "7E61D334-4025-41EF-9145-FC327B35301D"
}

Kode kesalahan

HTTP status code	Error code	Error message	Description
400	OperationFailed.AttachmentReferencedVpcRouteEntryExisted	Operation is failed because there is at least one route entry which next hop is the specified attachment.	The error message returned because this operation is not supported when a route points to an attachment.
400	OperationFailed.RouteTablePropagationExist	The specified TransitRouterAttachment has configured RouteTablePropagation. Please remove the configuration first.	The error message returned because you cannot perform the operation when a route learning correlation is configured for the network instance connection. Disassociate from the route learning correlation and try again.
400	OperationFailed.MulticastDomainAssociationExist	The specified TransitRouterAttachment has configured MulticastDomainAssociation. Please remove the configuration first.	The error message returned because the specified transit router attachment (TransitRouterAttachment) is added to a multicast domain. Remove the attachment from the multicast domain and try again.
400	OperationUnsupported.TransitRouterType	The specified TransitRouterType does not support the operation.	The error message returned because this operation is not supported by the specified type of transit router.
400	OperationFailed.PrefixListExist	Operation failed because PrefixList exists.	The error message returned because a prefix list exists.
400	InvalidTransitRouterAttachmentId.NotFound	TransitRouterAttachmentId is not found.	The error message returned because the ID of the network instance does not exist.
400	IncorrectStatus.VpcRouteEntry	The resource is not in a valid state for the attachment operation.	The error message returned because the status of the VPC route entry does not support this operation. Try again later.
400	IncorrectStatus.VpcSwitch	The resource is not in a valid state for the attachment operation.	The error message returned because the status of the vSwitch does not support this operation. Try again later.
400	IncorrectStatus.Vpc	The resource is not in a valid state for the operation.	The error message returned because the status of the VPC does not support this operation. Try again later.
400	OperationFailed.NotSupportForceDelete	Not support force delete attachment.	The error message returned because the specified resource cannot be forcefully deleted.
400	IncorrectStatus.VpcRouteTable	The VPC route table is not in a desired state.	The error message returned because the VPC route table is in an unstable state. Try again later.
400	OperationFailed.RouteEntryExist	Failed to delete the instance because a route table entry points to the instance.	Failed to delete the instance because one or more routes point to the instance. Delete the routes and try again.
400	OperationFailed.RouteTableAssociationExist	Operation failed because there is associated routing table.	The network connection deletion failed because there is an associated routing table.
400	IncorrectStatus.VpcResource	The resource is not in a valid state for the attachment operation.	The error message returned because this operation is not supported when the specified VPC is in an unstable state. Wait until all operations related to the VPC are completed.
400	OperationFailed.FlowLogExistOrNisOpened	Operation failed because FlowLog exists or Nis opened.	The error message returned because this operation is not supported when a flow log exists or the NIS service is activated.
400	InvalidParameter	Invalid parameter.	The error message returned because the parameter is set to an invalid value.
400	Unauthorized	The AccessKeyId is unauthorized.	The error message returned because you do not have the permissions to perform this operation.
400	OperationNotPermitted.AttachmentManagedByCloudService	The specified Attachment managed by cloud service can only be deleted through cloud service.

Lihat Error Codes untuk daftar lengkap.

Catatan rilis

Lihat Release Notes untuk daftar lengkap.