Support Network Peering parameters about pulumi-gcp HOT 9 CLOSED

We can close this out. If we run into this again we can always reopen it.

from pulumi-gcp.

Thanks to you both :)

from pulumi-gcp.

@fernandocarletti is this the right resource/setting for you? https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/compute/#NetworkPeeringArgs-autoCreateRoutes

This is the same as networkPeering.autoCreateRoutes at https://cloud.google.com/compute/docs/reference/rest/v1/networks/addPeering.

from pulumi-gcp.

@clstokes My issue is with networkPeering.exchangeSubnetRoutes, which export/import the custom routes in the peering VPC. That's the one I could not find a way to set in Pulumi.

from pulumi-gcp.

@fernandocarletti The description for networkPeering.autoCreateRoutes says This field will be deprecated soon. Prefer using exchangeSubnetRoutes instead. so I wonder if it has the same effect?

(We'll still need to address the deprecation of it.)

from pulumi-gcp.

@clstokes That's the problem. I can't use exchangeSubnetRoutes since there's no place I can set it: https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/compute/#NetworkPeering

from pulumi-gcp.

@fernandocarletti I think they are functionally equivalent. Can you set autoCreateRoutes in Pulumi and see if it works for you?

from pulumi-gcp.

Ping @fernandocarletti just circling back on this one before we either close it out or chase it down

from pulumi-gcp.

Hello @stack72. I believe in the end this feature wasn't used at Linio (@nesl247 can tell for sure). Seems like the options for configuring the peering in the GCP console are a bit different from the ones available in the API. As far as I remember with the autoCreateRoutes you can't select if you are just importing or just exporting, what was needed in the case I was working on.

TLDR I believe we can close this.

from pulumi-gcp.