NetworkPeeringResponse

data class NetworkPeeringResponse(val autoCreateRoutes: Boolean, val exchangeSubnetRoutes: Boolean, val exportCustomRoutes: Boolean, val exportSubnetRoutesWithPublicIp: Boolean, val importCustomRoutes: Boolean, val importSubnetRoutesWithPublicIp: Boolean, val name: String, val network: String, val peerMtu: Int, val stackType: String, val state: String, val stateDetails: String)

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.

Constructors

Link copied to clipboard
fun NetworkPeeringResponse(autoCreateRoutes: Boolean, exchangeSubnetRoutes: Boolean, exportCustomRoutes: Boolean, exportSubnetRoutesWithPublicIp: Boolean, importCustomRoutes: Boolean, importSubnetRoutesWithPublicIp: Boolean, name: String, network: String, peerMtu: Int, stackType: String, state: String, stateDetails: String)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

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

Link copied to clipboard

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.

Link copied to clipboard

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

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

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.

Link copied to clipboard

Maximum Transmission Unit in bytes.

Link copied to clipboard

Which IP version(s) of traffic and routes are allowed to be imported or exported between peer networks. The default value is IPV4_ONLY.

Link copied to clipboard

State for the peering, either ACTIVE or INACTIVE. The peering is ACTIVE when there's a matching configuration in the peer network.

Link copied to clipboard

Details about the current state of the peering.