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?

I added

ignoreChanges

to my resources but they are still showing up in

drift detection

. example:

const iam = new IAMMember(`${prefix}-${_account.accountId}-bq-editor-member`, {
  project: gcpConfig.require('project'),
  role: 'roles/bigquery.dataEditor',
  member: account.email.apply(email => `serviceAccount:${email}`)
}, { ignoreChanges: ['etag'] })

but it’s still showing up in the drift

pulumi refresh --preview-only

~ gcp:projects/iAMMember:IAMMember: (update)
...
--outputs:--
~ etag     : "BwYWTNS0Q6s=" => "BwYY98HnOng="

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hi, I am trying to setup my project with Pulumi, locally tsc gives no errors. When I use

pulumi up

it looks like typescript has some issues with a property that was added with Declaration Merging. I don't really understand why it's not working considering

tsc

is running fine

This message was deleted.

This message was deleted.