VMware Engine v1 API - Class DeleteExternalAccessRuleRequest (1.3.0)

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

Reference documentation and code samples for the VMware Engine v1 API class DeleteExternalAccessRuleRequest.

Request message for [VmwareEngine.DeleteExternalAccessRule][google.cloud.vmwareengine.v1.VmwareEngine.DeleteExternalAccessRule]

Inheritance

object > DeleteExternalAccessRuleRequest

Namespace

Google.Cloud.VmwareEngine.V1

Assembly

Google.Cloud.VmwareEngine.V1.dll

Constructors

DeleteExternalAccessRuleRequest()

public DeleteExternalAccessRuleRequest()

DeleteExternalAccessRuleRequest(DeleteExternalAccessRuleRequest)

public DeleteExternalAccessRuleRequest(DeleteExternalAccessRuleRequest other)
Parameter
NameDescription
otherDeleteExternalAccessRuleRequest

Properties

ExternalAccessRuleName

public ExternalAccessRuleName ExternalAccessRuleName { get; set; }

ExternalAccessRuleName-typed view over the Name resource name property.

Property Value
TypeDescription
ExternalAccessRuleName

Name

public string Name { get; set; }

Required. The resource name of the external access firewall rule to delete. Resource names are schemeless URIs that follow the conventions in https://cloud.google.com/apis/design/resource_names. For example: projects/my-project/locations/us-central1/networkPolicies/my-policy/externalAccessRules/my-rule

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 guarantees that a request doesn't result in creation of duplicate commitments for at least 60 minutes.

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 the 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