Fix deletion of Guacamole VM in stopped state

[marrobi]

Draft - what think about this approach with a script to ensure child resources are deleted? Need to do other VMs.

Add a configuration option to Guacamole VM templates to skip shutdown and force deletion, resolving the issue where VMs in a stopped state cannot be deleted. Update relevant Terraform and Porter files to implement this change and increment version numbers accordingly.

Fixes #4135

[marrobi]

@tamirkamara @jonnyry attempt number 2, thoughts on this approach?

[marrobi]

@dram1964 fancy testing this one?

[dram1964]

Hi @marrobi, I did test the original fix, but didn't realise that this left the os_disk deployed. Happy to test out the new code, but I was wondering whether this is the best approach.
Given that the virtual_machine {skip_shutdown_and_force_delete = true } feature is designed to preserve sub-resources of the VM, the additional script is a 'fix for the fix'.
Would it be better to add an az vm start operation to the 'delete' step, since the 'delete' operation appears to expect the vm to be started?

[marrobi]

Hi @marrobi, I did test the original fix, but didn't realise that this left the os_disk deployed. Happy to test out the new code, but I was wondering whether this is the best approach. Given that the virtual_machine {skip_shutdown_and_force_delete = true } feature is designed to preserve sub-resources of the VM, the additional script is a 'fix for the fix'. Would it be better to add an az vm start operation to the 'delete' step, since the 'delete' operation appears to expect the vm to be started?

Agree, that's another option, just worry about turning a VM on that has been intentionally stopped. Imagine it has a start-up script that does stuff, or you turn it off as it has some malware. I'd prefer to just get rid of it.

[tamirkamara]

Wouldn't it be easier to use azure cli to delete the VM if it's not on and then let TF do its thing without any other modification?
We already have the VM resource ID available so just need to query if it exists in the right state and delete.
p.s. there seem to be a PR on AzureRM for this. So probably should add a comment to any fix here that can be removed when will move to version 4.14 (maybe?)