This message was deleted.
# general
s
This message was deleted.
g
Can you use the
--target
flag on
up
and
destroy
to make the specific change you're needing to do?
b
even with
--target
it insists on completing deletes from the previous update
g
I see. Just to confirm if you do
pulumi stack export
do you see those pending deletes in
pending_operations
in the output?
b
i imagine i would, but let me check
yeah they are
if i remove them, import, update, then add the pending deletes back, would that work?
the pending deletes arent even there
in the state
i cant even
pulumi destroy
because the same thing happens...
even if i remove all references to the resource in the state file, pulumi up still tries to finish the delete. i guess those previous deletes are kept somewhere outside the state file?
ok my stack is completely broken now. cant destroy, can't update. unsure what to do here short of manually deleting all the resources
ok i managed to fix it by doing a series of manual deletes of some of the resources that were having issues , followed by
pulumi refresh
etc, eventually go there but it was pretty painful