So.. I've spent the past few weeks refactoring my pulumi code to ComponentResource spec - and I've got one outstanding question before I embark on a new world of pain.. Right now I have one primary ComponentResource for each resource type, with the provider specific resource directly underneath. I'm planning on making another change to create a new provider-type specific ComponentResource. Currently i have ComponentResource "network" which handles virtual networks, subnets, security groups, etc. What I want to do is introduce a Component Resource inside of the "network" one which is called "azure-net" so that the "network" resource can be cloud-agnostic (all network resources take pretty much the same configuration regardless of provider - so I'll be leveraging that with sensible defaults and overrides). My question is really this: My URNs will likely change when I perform the operation, and I'm creating ~40xN resources (where N is number of datacenters/regions it should span) for each stack - is there a sensible way of reimporting created resources? Current URN:

urn:pulumi:mystack::myproject::purpose:components:provider$purpose:components:group$purpose:components:k8s$azure-native:containerservice:ManagedCluster$random:index/randomUuid:RandomUuid::mystack-cluster-k8s-location-diskcrypto-to-kv-cert-RA

I'm guessing the

:components:k8s$azure-native:

bit is what's going to change. Initial thought: export the stack + search and replace + reimport stack? Any other ideas? Doing

pulumi import

on each one is.. just not going to work, besides taking a huge amount of time, it will just be really really really tricky to ensure I have the right URN specified for each resource.

You can use the alias opt, so that each resource has both its original URN and its new one.