mirror of https://github.com/pulumi/pulumi.git
e743503d37
Before actually writing the source stack, we have no way of knowing we can write it. The same is true for writing the destination stack. This means if the one we write later fails to write, we get an incompletely moved state. We've decided to move the destination stack first, and then the source stack, so resources are always tracked. The error message also mentions cleaning up the source stack, however it's not completely obvious how to do that. Since we know the resources that were supposed to be moved (and successfully been written to the destination stack at this point), we can give the user better instructions on how to clean up the resources. Do that by giving them a full set of `pulumi state delete` commands they can run to clean up the source stack. Fixes https://github.com/pulumi/pulumi/issues/17187 |
||
|---|---|---|
| .. | ||
| display | ||
| diy | ||
| filestate | ||
| httpstate | ||
| state | ||
| apply.go | ||
| apply_test.go | ||
| backend.go | ||
| backend_test.go | ||
| cancellation_scope.go | ||
| doc.go | ||
| errors.go | ||
| inmemoryPersister.go | ||
| mock.go | ||
| policypack.go | ||
| query.go | ||
| snapshot.go | ||
| snapshot_test.go | ||
| stack.go | ||
| updates.go | ||
| watch.go | ||