You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we always end up with a VM/VDI when the script is run. Either old ones when the script was run before and the user selected to not delete the files, or new ones. There is no option for the user to delete the files other than going into VirtualBox and doing it from there.
Requirements
[ ] Provide a method for listing and displaying the VM's created by KubuQA. It's important to not disturb the users VM, and we should not list them
[ ] Re ^ We're going to need a way to identify KubuQA Created VM's Perhaps a Prefix or Suffic maybe ?
[ ] Provide a Selection Dialog with a 'Uninstall' button, which will Uninstall / Remove the VM
[ ] Extend the command line options with a --list function
[ ] Extend the command line options with a --remove function
[ ] Extend the command line options with a --purge function which removes all KubuQA created VM
[ ] Untinstall of a VM should also automatically remove it's VDI, and Storage Controller
Considerations
For destructive methods, make sure it is clear that the items being removed will be permanently deleted
The text was updated successfully, but these errors were encountered:
Currently, we always end up with a VM/VDI when the script is run. Either old ones when the script was run before and the user selected to not delete the files, or new ones. There is no option for the user to delete the files other than going into VirtualBox and doing it from there.
ricktimmis
changed the title
Provide an "Uninstall" option
Provide an "Uninstall VM" option
Apr 18, 2024
Background
Currently, we always end up with a VM/VDI when the script is run. Either old ones when the script was run before and the user selected to not delete the files, or new ones. There is no option for the user to delete the files other than going into VirtualBox and doing it from there.
Requirements
Considerations
The text was updated successfully, but these errors were encountered: