No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

restore_stacks.gif

Learn more in the blog post: <https://www.pulumi.com/blog/restore-stacks/>

Social links for sharing!
• LinkedIn: <https://www.linkedin.com/feed/update/urn:li:activity:7087831752651534336>
• Twitter: <https://twitter.com/PulumiCorp/status/1682062809704681474>

<@U02E8Q3RN78> amazing! But I dont see this the three-dotted button. And I would really like to restore a stack.

ah, you need to be and Admin of the org in order to do this!

And you need a Enterprise plan. Maybe good to mention this kind of info in the blog :wink:

Are there details of how this is implemented?  Is it snapshot based?  Can I request a stack state from a few days ago be restored?

The feature just supports recovering from a deleted state, so the state the stack was in when it was deleted. 

Separately, Pulumi Cloud stores the state checkpoint file at every update. You can download the state file from any point in time and then rollback to that version using `pulumi stack import`. 

What if I've already deleted the stack, created it and refreshed?  Have I ruined the possibility of restoration?

We have a path forward, but restoring the state from a few days ago would be much easier for us to achieve a resolution.  I have filed a support ticket.

You should be able to restore a stack that has the same name as a current one. I can sync internally with whoever picks up the ticket. 

Have you tried seeing if it showed up under restore stack options? On the stacks page there should be a three dot menu to check. 

I have, but there are two issues.

1. I think because I attempted to init and refresh, I can only restore a stack with 0 resources
2. Maybe related, but I forced removal to abandon the stacks, because I was migrating the stack to an s3 state backend (only this project state wasn't migrated yet...)

It's not a critical stack, we could delete and recreate it, but I figured if we could restore from a few days ago, that would be like ctrl+z and save us some time/effort.

Okay got it. If it was just the stack name conflict it would show in the restore stacks list. Let’s see if the customer support ticket can resolve this. Thanks for the added details! 

Np, I added two other stacks in the ticket that would just make this task easier because of stack references and deletions