Open KaoruDev opened 2 years ago
Implementation notes: Within compute V1 there is a networks
resource type. Peerings is a sub-collection within the network resource, but is not its own resource. To add peerings, the custom methods addPeering
, updatePeering
and removePeering
must be used to modify the peerings within the network.
We could investigate using these methods indirectly to allow us to make the peerings colleciton modifyable, though ordering could be tricky here.
A similar pattern seems to appear within:
cloudshell > users > environments -> publicKey
compute > disks -> resourcePolicies
compute > firewallPolicies > association
compute > firewallPolicies > rule
compute > instances > resourcePolicies
compute > networks > peering
compute > regionDisks -> resourcePolicies
compute > securityPolicies > rule
compute > targetPools > healthCheck
datafusion (beta) > iamPolicy
firebasestorage > buckets > firebase
Hello!
Issue details
Please add support for setting up VPC peering, similar to https://www.pulumi.com/registry/packages/gcp/api-docs/compute/networkpeering/
Affected area/feature
Networking