ip_address_range = gcp.compute.GlobalAddress(
    "global-address",
    purpose="VPC_PEERING",
    address_type="INTERNAL",
    prefix_length=16,
    network=network.name,
)
gcp.servicenetworking.Connection(
    "private-connection",
    network=network.id,
    service="<http://servicenetworking.googleapis.com|servicenetworking.googleapis.com>",
    reserved_peering_ranges=[ip_address_range.name],
)

where

network

is an instance of

gcp.compute.Network

Make sure you have

<http://servicenetworking.googleapis.com|servicenetworking.googleapis.com>

service enabled. If you want to make it via pulumi as well:

service_networking_api = gcp.projects.Service(
    "servicenetworking",
    disable_dependent_services=True,
    service="<http://servicenetworking.googleapis.com|servicenetworking.googleapis.com>",
)

However then you’ll need to explicitly add

depends_on

in

gcp.servicenetworking.Connection

(or run

pulumi up

twice 😛):

gcp.servicenetworking.Connection(
        "private-connection",
        network=network.id,
        service="<http://servicenetworking.googleapis.com|servicenetworking.googleapis.com>",
        reserved_peering_ranges=[ip_address_range.name],
=>      pulumi.ResourceOptions(depends_on=[service_networking_api])
    )

Setting private IP on cloudsql instance itself is pretty straighforward:

...
ip_configuration=gcp.sql.DatabaseInstanceSettingsIpConfigurationArgs(
    private_network=network.id,
),
...

and again (unfortunately), the dependency between

gcp.servicenetworking.Connection

and

gcp.sql.DatabaseInstance

cannot be detected automatically, so you either have to make sure that private connection is created before you try to create database instance or use

depends_on

again to explicitly mark this fact

ok, that all makes sense. wouldn't have thought globaladdress was what I was looking for, as for the dependency checks, @helpful-hair-30515 good case for splitting it out into its own class and doing the checks there (against the config)

@wooden-battery-52855 that should work as well and as @prehistoric-activity-61023 mentioned to use stack references instead also a great choice!!!