🚀 Feat reattach to manual destroy run #594
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
baptman21
force-pushed
the
feat-reconnect-to-manual-destroy-run
branch
from
db0ff2c to
956f0dd
Compare
baptman21
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add the ability to manually retry a destroy run when deleting a workspace with DeletionPolicy set to destroy. Currently, if the destroy run created by the operator fails, manually running a destroy run does not reconcile the workspace, and it stays stuck in errored until the workspace is manually deleted.
This is not a retry from the operator, but allows a better handling of manual retries.
Usage Example
References
Fixes: GH-548
Community Note