This field will be deprecated soon. Useexchange_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 isACTIVE.
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.
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.
This field will be deprecated soon. Useexchange_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 isACTIVE.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-01-24 UTC."],[],[]]