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

No. This is normally done by using multiple projects. It can be wrapped into a single automation-api app, but you probably need multiple Pulumi projects.

Alright, so the idea is that I would first setup the VPC then request the spot fleet on pulumi up.
Then when destroying, I'd run pulumi destroy on the fleet, wait until it is done, then remove the VPC ?
How would this be orchestrated this via the automation api?

You can call any number of projects, either internal or external, from a single file in automation-api

Have you tried using `dependsOn` for the CustomResourceOptions of the spot fleet? If you force the spot fleet to depend to the vpc pulumi should ensure the spot fleet is destroyed before it starts destroying the vpc.

The problem is
&gt; Because pulumi doesn't wait for the ec2 instances of the spot request to be deleted
So it's already doing everything in the right order (which is where `dependsOn` would help), it's just too asynchronous and is treating "response to delete request received" as "delete request completed".

I managed to solve this by using automation api. I had to create a dummy stack to be able to query aws resources (the ec2 instances) once i detected they were deleted, moved to delete the vpc. Quite a workaround but it doesn't overcomplicate the solution.