Cannot update existing VMs due to Priority being set

[TheRSP]

Trying to update a VM which was created with an older version of farmer now fails as of #894

{
    "status": "Failed",
    "error": {
        "code": "BadRequest",
        "message": "The specified priority value 'Regular' cannot be applied to the Virtual Machine '...' since no priority was specified when the Virtual Machine was created. For more information, see http://aka.ms/AzureSpot/errormessages."
    }
}

[isaacabraham]

cc @bigjonroberts

[bigjonroberts]

I think it should be fairly straightforward to change it to only output when set. I should have a chance to peek at this tomorrow morning.

[ninjarobot]

I think this is fixed by #969 that @TheRSP contributed. It was just released yesterday, but does what you describe @isaacabraham. Unless the explicitly set a priority then no priority field is emitted.

[ninjarobot]

Fixed by #969