how does resource deletion ordering work? i'm running into a problem where when I try to delete a load balancer resource, it refuses to delete because there are resources still using the load balancer. if every resource that uses that load balancer uses one of its parameters in its resource definition, or has an explicit

dependsOn

, will that load balancer only be deleted after all resources that use it are deleted? what about transitive dependencies?

Yes, Pulumi will respect the resource graph during deletion. If you need to influence the graph using

dependsOn

, you will need to

up

after you make

dependsOn

changes to update the graph and then do a

destroy

.

hmm, i see. is that also true if i remove resources by removing code and then doing an

up

(as opposed to a

destroy

)?

Sorry, I don't follow the question.