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

Pulumi builds a directed acyclic graph of all operations it has to execute and tries to run as much as possible concurrently. Only when there are dependencies between resources, will there be an sequencing of these actions.
Can you elaborate a bit why you want `destroy` actions to run first?

I am assuming you mean destroy and recreate all the time? If that is it, a simple bash script with pulumi CLI commands can do the trick.

I have Gitlab resources that I have named `user-role` and when role changes I wanted do discard that resource but due to concurrency it was not rly possible, but in the end, I went with a different naming scheme so I should not need it.

One option I can think of is to use automation API and pick only destroy urns from `preview` and leave the rest for the 2nd `up`

<@U038KE6TFFD> which resource type from the Gitlab provider are you using for `user-role`

If possible, can you share a snippet of the code? I think you don’t have an Output dependency between some of the resources, which leads to Pulumi doing everything concurrently.

Hi <@UK4HNFLCB> correct there is no dependency, so to runs concurrently.
On top of that I found an issue in terraform gitlab provider, which completely breaks what intended to do :disappointed:
<https://github.com/gitlabhq/terraform-provider-gitlab/issues/1194>