This message was deleted.

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

@damp-spoon-83471 which resource type from the Gitlab provider are you using for

user-role

Hi @limited-rainbow-51650 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 😞 https://github.com/gitlabhq/terraform-provider-gitlab/issues/1194