Module network_peering

Manages a network peering within GCE. For more information see the official documentation and API.

Both networks must create a peering with each other for the peering to be functional.

Subnets IP ranges across peered VPC networks cannot overlap.

Example Usage

resources:
  peering1:
    type: gcp:compute:NetworkPeering
    properties:
      name: peering1
      network: ${default.selfLink}
      peerNetwork: ${other.selfLink}
  peering2:
    type: gcp:compute:NetworkPeering
    properties:
      name: peering2
      network: ${other.selfLink}
      peerNetwork: ${default.selfLink}
  default:
    type: gcp:compute:Network
    properties:
      name: foobar
      autoCreateSubnetworks: 'false'
  other:
    type: gcp:compute:Network
    properties:
      name: other
      autoCreateSubnetworks: 'false'

Import

VPC network peerings can be imported using the name and project of the primary network the peering exists in and the name of the network peering

• {{project_id}}/{{network_id}}/{{peering_id}}

When using the pulumi import command, VPC network peerings can be imported using one of the formats above. For example:

$ pulumi import gcp:compute/networkPeering:NetworkPeering default {{project_id}}/{{network_id}}/{{peering_id}}

Structs

• NetworkPeeringArgs
• NetworkPeeringArgsBuilder
  Use builder syntax to set the inputs and finish with build_struct().
• NetworkPeeringResult

Functions

• create
  Registers a new resource with the given unique name and arguments