Google Cloud Deploy v1 API - Class DeleteAutomationRequest (2.10.0) 

public sealed class DeleteAutomationRequest : IMessage<DeleteAutomationRequest>, IEquatable<DeleteAutomationRequest>, IDeepCloneable<DeleteAutomationRequest>, IBufferMessage, IMessage

Reference documentation and code samples for the Google Cloud Deploy v1 API class DeleteAutomationRequest.

The request object for DeleteAutomation.

Inheritance

object > DeleteAutomationRequest

Namespace

Google.Cloud.Deploy.V1

Assembly

Google.Cloud.Deploy.V1.dll

Constructors

DeleteAutomationRequest()

public DeleteAutomationRequest()

DeleteAutomationRequest(DeleteAutomationRequest)

public DeleteAutomationRequest(DeleteAutomationRequest other)
Parameter
NameDescription
otherDeleteAutomationRequest

Properties

AllowMissing

public bool AllowMissing { get; set; }

Optional. If set to true, then deleting an already deleted or non-existing Automation will succeed.

Property Value
TypeDescription
bool

AutomationName

public AutomationName AutomationName { get; set; }

AutomationName-typed view over the Name resource name property.

Property Value
TypeDescription
AutomationName

Etag

public string Etag { get; set; }

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.

Property Value
TypeDescription
string

Name

public string Name { get; set; }

Required. The name of the Automation to delete. Format should be projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}/automations/{automation_name}.

Property Value
TypeDescription
string

RequestId

public string RequestId { get; set; }

Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee 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).

Property Value
TypeDescription
string

ValidateOnly

public bool ValidateOnly { get; set; }

Optional. If set, validate the request and verify whether the resource exists, but do not actually post it.

Property Value
TypeDescription
bool