No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I manually deleted the loadbalancer resource which has allowed the other resources to be deleted. ¯\_(ツ)_/¯

That sounds like a dependency didn't track right, system should have been deleting the loadbalancer first. Might be needed an explicit dependsOn added if there weren't any implicit dependencies because of properties.

Perhaps - although that would have also affected the first `pulumi destroy` wouldn't it? Or is the order of the destroy non-deterministic?

Its non-deterministic because it tries to do as much as possible in parallel.