Delete running VMs with a single action.

[MichaelMallaburn]

Description

As a TRE Administrator/Researcher I want to be able to issue a single command to delete a VM regardless of its state.
So that I do not get distracted with another task and leave disabled VMs to exist longer than they should.

This will help with ephemeral VMs that exist solely to transfer between airlock storage containers and workspace network storage.

Acceptance criteria

• Criteria 1 - Delete option automatically schedules a disable, then deletion instead of user needing to do both.
• Criteria 2 - Optional - Ask for confirmation. I do not know if the two-stage "disable then delete" is to avoid erroneous deletion or for another reason, but this would help mitigate if so.

[CodeVishal-17]

This seems primarily like a workflow / UX limitation rather than an Azure API constraint.

Azure already supports deleting running VMs by implicitly stopping them first. TRE could expose a single delete --force (or equivalent UI action) that internally:

Checks VM state

If running → schedules disable/stop

Proceeds with deletion once safe

Optional confirmation could be gated behind a --force flag or UI checkbox to mitigate accidental deletes, while still allowing one-shot cleanup for ephemeral VMs.

[marrobi]

@MichaelMallaburn the two stage delete was to prevent accidental deletion, but also some orgs like to "archive" workspaces, so the idea of disable was a step further than stopped, where could also delete the resources without state so save costs etc. It hasn't been widely implemented.

So I think we need the intermediate state of disabled.

Something that could maybe added as an option somewhere, not sure.

[MichaelMallaburn]

That makes sense, and we are also using the disable state to save costs where resources are not in immediate use.

Currently, the UI, when clicking the ellipsis on a VM tile, has the delete option greyed out if the VM is not disabled.
A small change would be to allow the delete option to function in this state, but to have it perform the disable then delete step.

The existing delete functionality can remain as is when the service has already been disabled.

Would that be a good place to add it as an option?

[TonyWildish-BH]

@MichaelMallaburn, just want to make sure you're aware that Disabling a VM does not deallocate it, see #3973. You can have an open Guacamole session on a Disabled VM and it will still work just fine.