I'm trying to apply a Pulumi update that replaces a security group in AWS. Pulumi first tries to delete the security group before creating the replacement, however, the old security group is still in use and so AWS prevents the deletion (and Pulumi just hangs). How are folks orchestrating this kind of change?

There's a #CRH5ENVDX channel.

Thanks - I'll post this there as well

Import the security group first