This message was deleted.

I’m not sure exactly what resources you are getting this behavior, however, I’ll suggest to you try to use AWS Native provider, if you are not using that. Also, trying to conciliate your infrastructure as code getting the data to make decisions if you really need to push it or not. If you pass this decision to pulumi CLI it can continue in that direction because pulumi CLI doesn’t have this intelligence included, all resources will handle equally but some resources need better handled before provisioning repetitively. (https://www.pulumi.com/registry/packages/aws-native/api-docs/wafv2/)

Thanks for the reply. I'll give the native provider a shot since I'm using the classic one at the moment and see if that addresses it