This message was deleted.

It's a little hacky today, but you should be able to do the following: 1. Export the stack with

pulumi stack export

2. Create a new stack with the same name in the target organization

pulumi stack init <org-name>/<stack-name>

3. Import the stack you exported with

pulumi stack import

4. Since secret configuration is encrypted with a key tied to the stack itself, you'll have to (unfortunately) run

pulumi config set --secret <key> <value>

to reset any encrypted configuration you have. 5. You should now be able to

pulumi stack rm

the old stack. You don't want to run

pulumi destroy

.

ok - will give it a shot

This will be a little trickier. Since the URN of every resource includes both the stack name (sans organization) and project it is in, you'll have to manually export the stack and then edit the checkpoint to rename the stack name in the URN. and then import the new checkpoint, So between 2 and 3, edit the checkpoint you exported and replace

urn:pulumi:<old-stack-name>::

with

urn:pulumi:<new-stack-name>::

. @microscopic-florist-22719 Does that sound right to you?

I think so, yes. Note that the

import

will refuse to proceed if the stack name is incorrect, so at the very least we have belt and suspenders here.

this UX is pretty bad - creating the new stacks overwrote my config files

but how do i backup my secret key for later?

There's no concept of that today. The kye is created when a stack is initialized and managed by the service for the lifetime of the stack.

sigh this did not go well

we can help you out here, yes.

thank you!

can you DM me the name of the deleted stack?

yes, thanks