Reference documentation and code samples for the Compute V1 Client class NetworksAddPeeringRequest.
Generated from protobuf message google.cloud.compute.v1.NetworksAddPeeringRequest
Namespace
Google \ Cloud \ Compute \ V1
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ auto_create_routes
bool
This field will be deprecated soon. Use exchange_subnet_routes in network_peering instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.
↳ name
string
Name of the peering, which should conform to RFC1035.
Network peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (name, peer network, exchange_subnet_routes) in the network_peering field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.
↳ peer_network
string
URL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network.
getAutoCreateRoutes
This field will be deprecated soon. Use exchange_subnet_routes in network_peering instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.
Returns
Type
Description
bool
hasAutoCreateRoutes
clearAutoCreateRoutes
setAutoCreateRoutes
This field will be deprecated soon. Use exchange_subnet_routes in network_peering instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.
Parameter
Name
Description
var
bool
Returns
Type
Description
$this
getName
Name of the peering, which should conform to RFC1035.
Returns
Type
Description
string
hasName
clearName
setName
Name of the peering, which should conform to RFC1035.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getNetworkPeering
Network peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (name, peer network, exchange_subnet_routes) in the network_peering field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.
Network peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (name, peer network, exchange_subnet_routes) in the network_peering field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.
URL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network.
Returns
Type
Description
string
hasPeerNetwork
clearPeerNetwork
setPeerNetwork
URL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Compute V1 Client - Class NetworksAddPeeringRequest (1.35.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.35.0 (latest)](/php/docs/reference/cloud-compute/latest/V1.NetworksAddPeeringRequest)\n- [1.34.0](/php/docs/reference/cloud-compute/1.34.0/V1.NetworksAddPeeringRequest)\n- [1.33.0](/php/docs/reference/cloud-compute/1.33.0/V1.NetworksAddPeeringRequest)\n- [1.32.0](/php/docs/reference/cloud-compute/1.32.0/V1.NetworksAddPeeringRequest)\n- [1.31.0](/php/docs/reference/cloud-compute/1.31.0/V1.NetworksAddPeeringRequest)\n- [1.30.0](/php/docs/reference/cloud-compute/1.30.0/V1.NetworksAddPeeringRequest)\n- [1.29.0](/php/docs/reference/cloud-compute/1.29.0/V1.NetworksAddPeeringRequest)\n- [1.28.0](/php/docs/reference/cloud-compute/1.28.0/V1.NetworksAddPeeringRequest)\n- [1.27.0](/php/docs/reference/cloud-compute/1.27.0/V1.NetworksAddPeeringRequest)\n- [1.26.0](/php/docs/reference/cloud-compute/1.26.0/V1.NetworksAddPeeringRequest)\n- [1.25.0](/php/docs/reference/cloud-compute/1.25.0/V1.NetworksAddPeeringRequest)\n- [1.24.0](/php/docs/reference/cloud-compute/1.24.0/V1.NetworksAddPeeringRequest)\n- [1.23.0](/php/docs/reference/cloud-compute/1.23.0/V1.NetworksAddPeeringRequest)\n- [1.22.1](/php/docs/reference/cloud-compute/1.22.1/V1.NetworksAddPeeringRequest)\n- [1.21.0](/php/docs/reference/cloud-compute/1.21.0/V1.NetworksAddPeeringRequest)\n- [1.20.0](/php/docs/reference/cloud-compute/1.20.0/V1.NetworksAddPeeringRequest)\n- [1.19.0](/php/docs/reference/cloud-compute/1.19.0/V1.NetworksAddPeeringRequest)\n- [1.18.1](/php/docs/reference/cloud-compute/1.18.1/V1.NetworksAddPeeringRequest)\n- [1.17.0](/php/docs/reference/cloud-compute/1.17.0/V1.NetworksAddPeeringRequest)\n- [1.16.2](/php/docs/reference/cloud-compute/1.16.2/V1.NetworksAddPeeringRequest)\n- [1.14.0](/php/docs/reference/cloud-compute/1.14.0/V1.NetworksAddPeeringRequest)\n- [1.13.0](/php/docs/reference/cloud-compute/1.13.0/V1.NetworksAddPeeringRequest)\n- [1.12.1](/php/docs/reference/cloud-compute/1.12.1/V1.NetworksAddPeeringRequest)\n- [1.11.1](/php/docs/reference/cloud-compute/1.11.1/V1.NetworksAddPeeringRequest)\n- [1.10.1](/php/docs/reference/cloud-compute/1.10.1/V1.NetworksAddPeeringRequest)\n- [1.9.1](/php/docs/reference/cloud-compute/1.9.1/V1.NetworksAddPeeringRequest)\n- [1.8.3](/php/docs/reference/cloud-compute/1.8.3/V1.NetworksAddPeeringRequest)\n- [1.7.1](/php/docs/reference/cloud-compute/1.7.1/V1.NetworksAddPeeringRequest)\n- [1.6.1](/php/docs/reference/cloud-compute/1.6.1/V1.NetworksAddPeeringRequest)\n- [1.5.0](/php/docs/reference/cloud-compute/1.5.0/V1.NetworksAddPeeringRequest) \nReference documentation and code samples for the Compute V1 Client class NetworksAddPeeringRequest.\n\nGenerated from protobuf message `google.cloud.compute.v1.NetworksAddPeeringRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Compute \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getAutoCreateRoutes\n\nThis field will be deprecated soon. Use exchange_subnet_routes in network_peering instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.\n\n### hasAutoCreateRoutes\n\n### clearAutoCreateRoutes\n\n### setAutoCreateRoutes\n\nThis field will be deprecated soon. Use exchange_subnet_routes in network_peering instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.\n\n### getName\n\nName of the peering, which should conform to RFC1035.\n\n### hasName\n\n### clearName\n\n### setName\n\nName of the peering, which should conform to RFC1035.\n\n### getNetworkPeering\n\nNetwork peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (name, peer network, exchange_subnet_routes) in the network_peering field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.\n\n### hasNetworkPeering\n\n### clearNetworkPeering\n\n### setNetworkPeering\n\nNetwork peering parameters. In order to specify route policies for peering using import and export custom routes, you must specify all peering related parameters (name, peer network, exchange_subnet_routes) in the network_peering field. The corresponding fields in NetworksAddPeeringRequest will be deprecated soon.\n\n### getPeerNetwork\n\nURL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network.\n\n### hasPeerNetwork\n\n### clearPeerNetwork\n\n### setPeerNetwork\n\nURL of the peer network. It can be either full URL or partial URL. The peer network may belong to a different project. If the partial URL does not contain project, it is assumed that the peer network is in the same project as the current network."]]
