Does `pulumi destroy` respect the `dependsOn` opti...
# general
pulumi destroy
respect the
option? I have two custom component resources where one
the other, and it errors out because it destroys both in parallel. Anyway to make sure one is destroyed before the other?
It should, yes. There were a couple of issues addressed earlier this year, so if you are on an older CLI or Pulumi SDK, it's possible you are seeing one of those. One of them is If you are on latest of CLI and SDK and seeing something like this, it would be helpful to get more details (ideally a repro) of the arrangement of the resources and components, to ensure whether this is behaving correctly or not.