No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

it should do that as part of the bridge, is there something not working?

im using the vsphere module, which is based on TF

resource_name is not option, so I am just providing “VirtualMachine” as resource name, and I was hoping that it will be prefixed or suffixed with a random id

but instead, if I attempt to create two VM’s, the 2nd will complain about lack of URN uniqueness

btw your public repo’s help me a lot to create pulumi provider + build pipeline from a tf module, so thx for that :)

well, its not simplified, sorry about that

line 163 is the one that causes the issues

basically, if I dont ensure that its unique, I will get errors like `Diagnostics:`
  vsphere:index:VirtualMachine (VirtualMachineAAA):
    error: Duplicate resource URN ‘urn:pulumi:dev::vinci-pulumi-win-desktop::vsphere:index/virtualMachine:VirtualMachine::VirtualMachineAAA’; try giving it a unique name```

if you specify the name of the machine, it won't autoname, if you remove that it should work

that prevens the auto naming, the guide even said so

no, the names are the same, it should be:
```import pulumi_random
a = pulumi_random.RandomPassword("password-a", length=8)
b = pulumi_random.RandomPassword("password-b", length=8)```

ok, so I do have to ensure that the resource name is unique?

so what’s the best way to deal with that if I want to automate that, but also dont want to resource names to change on each run?

the resource names shouldn't change on each run, it's a declarative state

im trying to create simpler interfaces for the resources I want to use, and ideally, the users of the simplified resources wouldnt have to deal with resource names

sorry I'm havinga hard time understanding :disappointed:
If you're creating a component you don't always need to specify the names of each resource, but the component itself still needs a name when it's declared

I will revisit this tomorrow with a fresh pair of eyes