Make the hypervisor spec immutable on termination#249
Merged
Conversation
It is hard to undo the termination in certain situations and the field should usually be set by an automation, so uncommiting to terminate a node is a rather less common scenario. So let's prohibit it for now. HA events can always happen, so we still need to be able to switch to that, and then anything goes.
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
anokfireball
approved these changes
Feb 27, 2026
toanju
approved these changes
Feb 27, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
It is hard to undo the termination in certain situations and the field should usually be set by an automation, so uncommiting to terminate a node is a rather less common scenario. So let's prohibit it for now.
HA events can always happen, so we still need to be able to switch to that, and then anything goes.