Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Improved recovery for invalid stacks #1094
If an update is interrupted partway through, it is possible that the service's understanding of your stack's state will have drifted from reality. The Pulumi CLI and service have no way of reconciling this drift today, and react conservatively by marking the state as "unknown." The result is the following error message:
To recover from this situation, you will need to do three things:
Depending on where we land with #1077, we may or may not need to invest in better recovery for invalid stacks. An invalid checkpoint occurs when an update interruption happens at an inopportune moment. There are ways we could possibly recover from this, for instance, if we knew that the local machine had reached a steady state prior to the interruption. Alternatively, we may just want to make the UX better, by interactively prompting the user for what they want to do next -- including possibly doing an interactive refresh to repair the state of the stack from the source of truth.