https://pulumi.com logo
#general
Title
# general
i

important-leather-28796

10/30/2019, 3:58 PM
I’m working on a new gcp cluster/stack and have free reign to destroy. I messed up some things and it looks like a cluster was replaced, unfortunately another cluster was lingering so I deleted via the console. Next
pulumi up
referenced something about deleting the old cluster still in progress. Regardless, old cluster is gone, but my stack thinks not. A
pulumi refresh
yields
Preview failed: Get <https://34.70.69.68/api?timeout=32s>: dial tcp 34.70.69.68:443: i/o timeout
. I’m just looking to fully destroy, then move forward again - how can I get synced and destroyed when
refresh
is failing?
Ah yes, it’s coming back to me. export/edit/import.
Copy code
pulumi stack export --file stack.json
# manual edit
pulumi stack import --file stack.json
pulumi destroy -y
2 Views