self-hosted-runners: do not deallocate by default

We will soon be adding logic that automatically spins up and removes
runners on-demand, so there's no need to deallocate in that case. An
additional benefit of not deallocating is that we can leverage the fast
D:\ drive to install the Runner on. This drive would otherwise be
destroyed as part of the deallocation process.

Signed-off-by: Dennis Ameling <[email protected]>

Author: dennisameling

.github/workflows/create-azure-self-hosted-runners.yml

@@ -27,7 +27,7 @@ on:
         type: boolean
         required: true
         description: Deallocate the runner immediately after creating it (useful for spinning up runners preemptively)
-        default: true
+        default: false
 
 env:
   AMOUNT_OF_RUNNERS: ${{ github.event.inputs.amount_of_runners }}