Glad that Terraform finally fixed this. It used to be an absolute pain to work out IDs before. Hopefully Pulumi can find a way to import their docs for the ID attribute

And this holds true for every provider, not just Google. It's because behind the scenes,

import

and

get

use the same RPC call.

I'm stuck on this again for the

IAMBinding

resource. @stocky-restaurant-98004 when you say it's the same as the ID for

import

which import do you mean?

like this?

terraform import google_storage_bucket.sample sample-project/my-bucket

i figured this out through trial and error 😂

for an iambinding you need the

name

of the resource and the unique provider ID is the

project NAME

and

role

i was trying to use

project NUMBER

because that's what pulumi stores in the resources

The problem is that the Google TF provider puts all 3 IAM resources in a single docs page, which makes conversion to the Pulumi registry tricky. (No other provider I know of does this.)

Here's a page that renders correctly: https://www.pulumi.com/registry/packages/aws/api-docs/ec2/vpc/#import In the import command, you can see:

VPCs can be imported using the vpc id, e.g.,

pulumi import aws:ec2/vpc:Vpc test_vpc vpc-a01106c2

That VPC id is the same value that should be passed to

.get()

if you want to grab it in a Pulumi program rather than import it because behind the scenes, they both make the same API call.

We really need to add to the docs for

get()

something like "see the Import section for details on how to formulate the ID parameter"

I logged an issue here a while ago, but I'll ping the team about it now and see if we can make this a little better: https://github.com/pulumi/pulumi-terraform-bridge/issues/609