This message was deleted.

No there isn't. Editing the state like this is something that you probably don't want to do regularly

Yeah unfortunately this comes from needing to migrate a lot of resources from Azure -> Azure Native. Which means deleting all the dependencies from the state before reimporting everything.....

Ah of course

could you loop over it using your shell?

That's pretty much what I was doing @handsome-state-59775, but it takes maybe a minute or more each time. Not ideal on a couple hundred resources....

for resource in "${resource_list[@]}"; do
    pulumi state delete "${resource}" -y &  # HOW ABOUT THIS?
done

wondering if concurrent deletes are safe... @brave-planet-10645?

That is a question I'm going to have to ask internally... BRB

Yeah not surprised with that at all, it shows it as an "Import" action in the webui when you run

pulumi state delete

so I imagine it's exporting the stack, modifying it and reimporting it? Doing that concurrently....nope.

Obviously you could run it not concurrently, but yes as you say if you've got a lot of resources it will take a while

Yeah in the end I exported the stack, edited it in vscode and reimported it. Preview is looking better but not upped it yet (Did find one case of accidentally deleting something that shouldn't have been, but it threw an error about that during import at least. Reinforces why I was trying to avoid manual state edits....)