unplug#1546
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideIntroduces a special case in the provisioning comparator to handle removal of provisioning without requiring a VM restart by emitting an immediate apply change. Sequence diagram for provisioning removal without VM restartsequenceDiagram
participant VMController
participant "compareProvisioning()"
participant VM
VMController->>"compareProvisioning()": Compare current and desired VM specs
"compareProvisioning()"->>VMController: Return FieldChange with ActionApplyImmediate if provisioning removed
VMController->>VM: Apply provisioning removal immediately (no restart)
Class diagram for updated compareProvisioning logicclassDiagram
class VirtualMachineSpec {
+Provisioning
}
class FieldChange {
+Operation
+Path
+CurrentValue
+DesiredValue
+ActionRequired
}
class compareProvisioning {
+compareProvisioning(current: VirtualMachineSpec, desired: VirtualMachineSpec): []FieldChange
}
VirtualMachineSpec <.. compareProvisioning
FieldChange <.. compareProvisioning
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Signed-off-by: Valeriy Khorunzhin <valeriy.khorunzhin@flant.com>
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: cancelled. |
1 similar comment
|
Workflow has started. The target step completed with status: cancelled. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: cancelled. |
Description
Why do we need it, and what problem does it solve?
What is the expected result?
Checklist
Changelog entries