This message was deleted.
s
This message was deleted.
v
Was the resource deleted manually? I’d have thought a refresh would’ve fixed it. I’ve seen similar errors with my stacks where the pod still exists in k8s in the deleting state for a long time so pulumi thinks it’s already there, but never seen the problem you’ve got
b
The pod was deleted when K8s was trying to recreate, unfortunately the pod was then deleted but the pulumi state file was not updated properly so now, I have the production pod deleted, all the other production resources live, but I can’t restore the deleted pod using a refresh nor a up and I don’t know how to solve the issue unfortunately
v
You could try temporarily removing the dependsOn dependencies in tbe code, running a pulumi up, deleting the resource from state then adding the dependsOn back and running pulumi up again?
b
I’ll try for sure! Thanks a lot for the suggestion. I’ll let you know how it will go
Hey @victorious-church-57397 your suggestion worked like a charm. Thanks a lot for your suggestion!
👍 1