Compute Engine v1 API - Class NetworkPeering (3.0.0)

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

A network peering attached to a network resource. The message includes the peering name, peer network, peering state, and a flag indicating whether Google Compute Engine should automatically create routes for the peering.

This field will be deprecated soon. Use the exchange_subnet_routes field 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.

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.

Whether to export the custom routes to peer network. The default value is false.

Whether subnet routes with public IP range are exported. The default value is true, all subnet routes are exported. IPv4 special-use ranges are always exported to peers and are not controlled by this field.

Gets whether the "auto_create_routes" field is set

Gets whether the "exchange_subnet_routes" field is set

Gets whether the "export_custom_routes" field is set

Gets whether the "export_subnet_routes_with_public_ip" field is set

Gets whether the "import_custom_routes" field is set

Gets whether the "import_subnet_routes_with_public_ip" field is set

Gets whether the "name" field is set

Gets whether the "network" field is set

Gets whether the "peer_mtu" field is set

Gets whether the "stack_type" field is set

Gets whether the "state" field is set

Gets whether the "state_details" field is set

Whether to import the custom routes from peer network. The default value is false.

Whether subnet routes with public IP range are imported. The default value is false. IPv4 special-use ranges are always imported from peers and are not controlled by this field.

Name of this peering. Provided by the client when the peering is created. The name must comply with RFC1035. Specifically, the name must be 1-63 characters long and match regular expression [a-z]([-a-z0-9]*[a-z0-9])?. The first character must be a lowercase letter, and all the following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

The 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.

Maximum Transmission Unit in bytes.

Which IP version(s) of traffic and routes are allowed to be imported or exported between peer networks. The default value is IPV4_ONLY. Check the StackType enum for the list of possible values.

[Output Only] State for the peering, either ACTIVE or INACTIVE. The peering is ACTIVE when there's a matching configuration in the peer network. Check the State enum for the list of possible values.

[Output Only] Details about the current state of the peering.