I'm really struggling with handling dependencies. I have a component that I wrote which creates a vnet, list of subnest, public IPs, NSGs, route tables, their routes and rules, etc. However, I wanted to replace an NSG to update the name. Of course, I don't have logic to handle removing and re-adding a subnet so I can re-create the NSG. I'm surprised that Pulumi doesn't handle this for me since the dependencies are known. How does everyone else handle this situation?

import ?

It's already in my state.

#comment it out in the code

#run pulumi, wait for it to remove it

#uncomment add changes ?

Pulumi generally will handle replacing resources that depend on a resource that is being replaced. Sometimes you have to explicitly tell Pulumi about that relationship if it's not explicit in the resource inputs (Resource Option: dependsOn)

@salmon-guitar-84472 That's the exact scenario I want to avoid. Ideally, it would create the new resource, associate it, then tear down the old one.

I believe this is where Pulumi hits the ceiling at the moment, we've found that any changes to vnet (which are not that uncommon IRL) are unfortunately very tricky and can easily end up with a lot of manual work and dealing with state discrepancies