This message was deleted.

I had the same problem but when I deleted the local project before getting pulumi to destroy the cloud version. It's a bit of an annoying part of Pulumi but probably a necessary evil so that they can avoid using cloudformation.

Yeah, I can understand it's not easy to handle region switching like that

While I'm not sure how it works, I think they could 'get around this' by just allowing the pulumi cli to use the already stored stack state in the pulumi servers to destroy an existing set of resources

Isn't that the case ?

I thought we had an issue tracking this - but couldn't find it so I opened https://github.com/pulumi/pulumi/issues/1593. Currently,

pulumi

always uses a single set of configuration for any given cloud provider during an update - so one you change your

aws:region

to

eu-west-1

, all calls to AWS from Pulumi will go to Ireland not Virginia. However, the delete operations on the old resources should instead use the provider configuration that was used to create them. This is something we plan to address. Fortunately, this should be fairly rare, and as you noticed later, you can work around by switching region back, destroying, then moving region forward (or standing up a new stack for the new region and destroying the old stack).

@able-tomato-34262 it wasn't the case when I tried. I have a stack that still exists in AWS that I can't delete because I removed the files from my laptop and pulumi won't let me run the command to tear the stack down. /shrug

Is it not possible to import a state file ?

no idea

I would know how to do it with terraform if you kept the state file but lost everything else but I don't think you can manually update the state file in pulumi @big-soccer-75859

I was thinking about just creating a barebones pulumi project and setting all the config to what it was before and trying to destroy it that way but I'm not sure if that'll work

I don't think so since you won't have the same state file on your new stack/project

hrmm, fair enough

I'm pretty sure there is one on the pulumi servers for each stack, they need to keep track of the things pulumi configured

oh right

Yeah, I think so

I guess so long as the local config matches the naming of things on their servers I should be able to run the command

Maybe create a new pulumi account and add that account to the organization that was created in the first place

yeh

It's possible to export the state using the

pulumi stack export

command (and import it using

pulumi stack import

).