one additional question, how hard is it to make pulumi just delete the resource group instead of deleting resources one by one (if the resource group is defined in the configuration). this is whats bugging me the most in terraform flow (and same happens here)

The short answer is “hard”. The longer answer is that Pulumi tries very hard to track every resource individually so that it can gracefully handle small changes in your infrastructure code and not have to e.g. create and destroy whole resource groups whenever their contents change. However, that means we can’t efficiently delete resource groups.

on the other hand, its just a graph of dependencies? if you detect that resources depend on one another, you can just get the top of the graph and delete it?