Class DeleteAutomationRequest (1.19.1)

Version 1.19.1

• 2.5.0 (latest)
• 2.4.1
• 2.3.0
• 2.2.0
• 2.1.0
• 2.0.0
• 1.19.1
• 1.18.1
• 1.17.3
• 1.16.0
• 1.15.0
• 1.14.0
• 1.13.0
• 1.12.0
• 1.11.1
• 1.10.1
• 1.9.0
• 1.8.0
• 1.7.0
• 1.6.1
• 1.5.0
• 1.4.1
• 1.3.1
• 1.2.1
• 1.1.1
• 1.0.0
• 0.3.2
• 0.2.0
• 0.1.1

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

The request object for DeleteAutomation.

Attributes
Name	Description
name	str Required. The name of the Automation to delete. Format should be projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}/automations/{automation_name}.
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 knows to ignore the request if it has already been completed. The server guarantees that for at least 60 minutes after 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, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
allow_missing	bool Optional. If set to true, then deleting an already deleted or non-existing Automation will succeed.
validate_only	bool Optional. If set, validate the request and verify whether the resource exists, but do not actually post it.
etag	str Optional. The weak etag of the request. This checksum is computed by the server based on the value of other fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding.