Compute Engine v1 API - Class DeleteRegionHealthCheckServiceRequest (2.10.0)

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

Reference documentation and code samples for the Compute Engine v1 API class DeleteRegionHealthCheckServiceRequest.

A request message for RegionHealthCheckServices.Delete. See the method description for details.

Inheritance

object > DeleteRegionHealthCheckServiceRequest

Implements

IMessage DeleteRegionHealthCheckServiceRequest, IEquatable DeleteRegionHealthCheckServiceRequest, IDeepCloneable DeleteRegionHealthCheckServiceRequest, IBufferMessage, IMessage

Inherited Members

object.GetHashCode()

object.GetType()

object.ToString()

Namespace

Google.Cloud.Compute.V1

Assembly

Google.Cloud.Compute.V1.dll

Constructors

DeleteRegionHealthCheckServiceRequest()

public DeleteRegionHealthCheckServiceRequest()

DeleteRegionHealthCheckServiceRequest(DeleteRegionHealthCheckServiceRequest)

public DeleteRegionHealthCheckServiceRequest(DeleteRegionHealthCheckServiceRequest other)

Parameter
Name	Description
`other`	`DeleteRegionHealthCheckServiceRequest`

Properties

HasRequestId

public bool HasRequestId { get; }

Gets whether the "request_id" field is set

Property Value
Type	Description
`bool`

HealthCheckService

public string HealthCheckService { get; set; }

Name of the HealthCheckService to delete. The name must be 1-63 characters long, and comply with RFC1035.

Property Value
Type	Description
`string`

Project

public string Project { get; set; }

Project ID for this request.

Property Value
Type	Description
`string`

Region

public string Region { get; set; }

Name of the region scoping this request.

Property Value
Type	Description
`string`

RequestId

public string RequestId { get; set; }

An optional 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. 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
Type	Description
`string`