Support deploy from known config for Orka provider
What does this MR do?
We currently deploy from a specified image, creating a VM configuration on-the-fly and deploy from it.
This MR allows a DeployFromConfig mode, where we instead deploy from a known VM configuration. Pre-created VM Configurations already contain the image to boot from. The job's image, will now refer to the known VM configuration, but this difference is transparent to the end-user.
This change allows us to create VMs with saved-state and additional options enabled such as IO Boost. Known configs will be deployed as we deploy new supported images.
Why was this MR needed?
To take advantage of the additional settings and VMs with saved state, to improve boot times.
What's the best way to test this MR?
Will update.
What are the relevant issue numbers?
Closes #89 (closed)
Edited by Arran Walker