Class DeleteMulticloudDataTransferConfigRequest (2.13.0)

Version latest

• 2.13.0 (latest)
• 2.12.0
• 2.11.0
• 2.10.0
• 2.9.0
• 2.8.1
• 2.7.1
• 2.6.0
• 2.5.1
• 2.4.5
• 2.3.0
• 2.2.0
• 2.0.2
• 1.6.1
• 1.5.0
• 1.4.4
• 1.3.2
• 1.2.2
• 1.1.0
• 1.0.1
• 0.6.3
• 0.5.0
• 0.4.0
• 0.3.0
• 0.2.0
• 0.1.0

DeleteMulticloudDataTransferConfigRequest(
    mapping=None, *, ignore_unknown_fields=False, **kwargs
)

Request message to delete a MulticloudDataTransferConfig resource.

Attributes
Name	Description
name	str Required. The name of the MulticloudDataTransferConfig resource to delete.
request_id	str Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server can ignore the request if it has already been completed. The server waits for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, can ignore the second request. This prevents clients from accidentally creating duplicate MulticloudDataTransferConfig resources. The request ID must be a valid UUID with the exception that zero UUID (00000000-0000-0000-0000-000000000000) isn't supported.
etag	str Optional. The etag is computed by the server, and might be sent with update and delete requests so that the client has an up-to-date value before proceeding.