Pulumi: ignore manually deleted resources during `pulumi up`

Question

I'm attempting to run a pulumi up command but it's failing because some of the resources that're being replaced were already manually deleted in the GCP Kubernetes dashboard. Is there a way to ignore the fact that these resources have already been deleted and continue with the update?

Answer 1

Run pulumi refresh which will reach out to GCP resources and will update the current state file in Pulumi