Compute Engine v1 API - Class AddPeeringNetworkRequest (2.2.0)

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

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

A request message for Networks.AddPeering. See the method description for details.

Inheritance

Object > AddPeeringNetworkRequest

Implements

IMessage<AddPeeringNetworkRequest>, IEquatable<AddPeeringNetworkRequest>, IDeepCloneable<AddPeeringNetworkRequest>, IBufferMessage, IMessage

Inherited Members

Object.GetHashCode()

Object.GetType()

Object.MemberwiseClone()

Object.ToString()

Namespace

Google.Cloud.Compute.V1

Assembly

Google.Cloud.Compute.V1.dll

Constructors

AddPeeringNetworkRequest()

public AddPeeringNetworkRequest()

AddPeeringNetworkRequest(AddPeeringNetworkRequest)

public AddPeeringNetworkRequest(AddPeeringNetworkRequest other)

Parameter
Name	Description
`other`	`AddPeeringNetworkRequest`

Properties

HasRequestId

public bool HasRequestId { get; }

Gets whether the "request_id" field is set

Property Value
Type	Description
`Boolean`

Network

public string Network { get; set; }

Name of the network resource to add peering to.

Property Value
Type	Description
`String`

NetworksAddPeeringRequestResource

public NetworksAddPeeringRequest NetworksAddPeeringRequestResource { get; set; }

The body resource for this request

Property Value
Type	Description
`NetworksAddPeeringRequest`

Project

public string Project { get; set; }

Project ID for 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`