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

Running `pulumi down` on a stack with a VPC and a ipam pool sets the cidr in a failed-provision state and locks the entire thing. I cannot remove it because Pulumi deleted the VPC but the CIDR refuses to deprovision because of this.

For cases like this you should leverage the dependsOn resourceOption to control deletion more closely.

Oh, good point. I just assumed it knew the order of everything as that was my experience from pulumi+azure. Thanks :+1:

I guess the problem is that the IPAMpool depends on the VPC to be deleted first, but the VPC has a dependency on IPAMpool when being creatged