https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
i
(is that your scenario?)
b
@incalculable-sundown-82514 yeah, we had a resource deleted by hand so now I have to edit the state manually
i
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
b
yeah, its just id prefer the CI/CD do it rather than by hand
we run refresh before every update
i
gotcha.
b
thanks for the follow up
i
yeah, 
pulumi state delete
is only useful for one-time disaster recovery. no problem!
cc @microscopic-florist-22719
m
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.
b
Copy code
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.
m
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by