[User story] delete

[gbraad]

Description

This command deletes the VM and related files from the disk.

The VM files are stored in ~/.crc/machines/crc/

This command is passed to the hypervisor manager and therefore might not perform a stop beforehand. This depends on the driver.

Options

• -f (force)
  When -f is used, we perform a delete from the driver and forcibly remove the files from the disk under ~/.crc/machines/crc.

[jsliacan]

Exit codes: Can crc delete ever fail except for vacuously (when VM does not exist)?

Behavior:

Default:

Is crc delete -f equivalent to rm -rf ~/.crc/machines/crc/*? If not, what happens if a user does this instead of crc delete -f?

Modified:

-f: Is there a practical difference between crc delete and crc delete -f in terms of destroying the VM? The side-effect of -f on this command is not being asked y/N for confirmation.

--clear-cache: delete ~/.crc/machines/crc/<this machine> and ~/.crc/cache? Does --clear-cache ever fail? What happens then?

--output: json? Then crc delete -o json always exits with 0 and JSON output contains the exit status?

[adrianriobo]

Add also a link to this possible enhancement on delete (contexts removal) #2375

[adrianriobo]

Delete now takes care of CRC context, should we inspect the state for the file after crc delete? Ensure only affects to crc contexts? also related to https://github.com/code-ready/tray-macos/issues/112

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.