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

I feel like failed resources should never stop a `pulumi refresh` from running. Is there an issue filed for that?

<https://github.com/pulumi/pulumi/issues/2352> ?

<@UB27BHS4B> yeah, we had a resource deleted by hand so now I have to edit the state manually

gotcha! re: editing the state, can you use this command? <https://pulumi.io/reference/cli/pulumi_state_delete.html>

it’s somewhat new, it’s designed to keep you from having to manually edit the state in a text editor

yeah, its just id prefer the CI/CD do it rather than by hand

yeah, `pulumi state delete` is only useful for one-time disaster recovery. no problem!

&gt;  yeah, we had a resource deleted by hand so now I have to edit the state manually

What kind of resource? `refresh` should be able to handle deleted resources.

```Diagnostics:
  kubernetes:extensions:Ingress (external-rpc):
    error: Preview failed: 2 errors occurred:

    * Resource 'external-rpc-2hxv283a' was created but failed to initialize
    * Ingress .status.loadBalancer field was not updated with a hostname/IP address.
        for more information about this error, see <https://pulumi.io/xdv72s>

error: an error occurred while advancing the preview
make: *** [refresh] Error 255```

One of the underlying target groups was deleted so the Ingress resource never fully built the ALB/ELB out

it would be awesome if the urn for the item was also mentioned in the error.

Ah, got it. This is exactly <https://github.com/pulumi/pulumi/issues/2352>.