This message was deleted.

Not totally sure what your asking for here? All pulumi logical names must be unique, the engine will error if a program tries to register the same name twice. By default pulumi will append random characters to the end of physical names (what's sent to the cloud provider) to try and ensure global uniqueness.

Okay, I'll try to be a little clearer. I'm trying for example to do something like this:

for subnet, nat_gateway in zip(
            subnets["subnets_objects"], nat_gateway_objects):

    private_route_table = RouteTable(
                f'myRouteTableExample-{region_suffix}',
    vpc_id=vpc.output.id,
    routes=[{"cidr_block": "0.0.0.0/0",
          "target_id": nat_gateway.id}])

Here I am trying to create several route tables dynamically, which I am iterating inside a for loop but the problem is that the resource_name would be the same and I would have to program something so that this resource_name is not repeated. What I want to know is if Pulumi provides a solution for this or should I implement something additional.

Yeh you need to do something custom there, probably putting the subnet and nat id's as part of the name or something

Ok, thanks for the quick response

Why wouldn't autonaming work here? Multiple

RouteTable

instances are created, and get postfixed, no?

They each need a unique logical name as well

It seems to me that autonaming could cover cases like these as well, in the future.

Maybe, but it starts getting into really hard to debug cases based on program ordering.

Combined with timestamped logging, it would work..

I don't think it would, logical names are used for state tracking and the timestamp or program order of them isn't a feature we can safely track by