NetworkPeeringResponseComputeBeta constructor

const NetworkPeeringResponseComputeBeta({
  1. required Input<bool> autoCreateRoutes,
  2. required Input<bool> exchangeSubnetRoutes,
  3. required Input<bool> exportCustomRoutes,
  4. required Input<bool> exportSubnetRoutesWithPublicIp,
  5. required Input<bool> importCustomRoutes,
  6. required Input<bool> importSubnetRoutesWithPublicIp,
  7. required Input<String> name,
  8. required Input<String> network,
  9. required Input<int> peerMtu,
  10. required Input<String> stackType,
  11. required Input<String> state,
  12. required Input<String> stateDetails,
})

Creates a new NetworkPeeringResponseComputeBeta. autoCreateRoutes 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. exchangeSubnetRoutes 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. exportCustomRoutes Whether to export the custom routes to peer network. The default value is false. exportSubnetRoutesWithPublicIp 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. importCustomRoutes Whether to import the custom routes from peer network. The default value is false. importSubnetRoutesWithPublicIp 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 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. network 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. peerMtu Maximum Transmission Unit in bytes. stackType Which IP version(s) of traffic and routes are allowed to be imported or exported between peer networks. The default value is IPV4_ONLY. state State for the peering, either ACTIVE or INACTIVE. The peering is ACTIVE when there's a matching configuration in the peer network. stateDetails Details about the current state of the peering.

Implementation

const NetworkPeeringResponseComputeBeta({
  required this.autoCreateRoutes,
  required this.exchangeSubnetRoutes,
  required this.exportCustomRoutes,
  required this.exportSubnetRoutesWithPublicIp,
  required this.importCustomRoutes,
  required this.importSubnetRoutesWithPublicIp,
  required this.name,
  required this.network,
  required this.peerMtu,
  required this.stackType,
  required this.state,
  required this.stateDetails,
});