Ability to fail deployment on failed VM runCommands

[matferrari-msft]

When deploying a VM, I use a run command in my bicep template to it. I cannot use cloud-init because the commands need to run after the extensions have been successfully added. A run command will successfully provision regardless of the exit status of the script. It would be nice to have a way to fail the deployment if the runCommand.properties.instanceView.exitStatus was not 0. Otherwise, the deployment succeeds and I think everything is good to go, when in reality the configuration failed. Below is an example:

resource configPart1 'Microsoft.Compute/virtualMachines/runCommands@2022-11-01' = {
  name: 'configPart1'
  parent: vm
  location: location
  properties: {
    protectedParameters: [{
        name: VAR_1
        value: VALUE_1
    }]
    source: {
      script: '/oops'
    }
  }
}

if (configPart1.properties.instanceView.exitStatus) {
    throw error
}

[anthony-c-martin]

Feels related to Azure/bicep#2405

[stephaniezyen]

We will track the improvement on the issue linked, but will also route it to the VM Resource Provider.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT. Please see https://aka.ms/biceptypesinfo for troubleshooting help.

Issue Details

---

When deploying a VM, I use a run command in my bicep template to it. I cannot use cloud-init because the commands need to run after the extensions have been successfully added. A run command will successfully provision regardless of the exit status of the script. It would be nice to have a way to fail the deployment if the runCommand.properties.instanceView.exitStatus was not 0. Otherwise, the deployment succeeds and I think everything is good to go, when in reality the configuration failed. Below is an example:

resource configPart1 'Microsoft.Compute/virtualMachines/runCommands@2022-11-01' = {
  name: 'configPart1'
  parent: vm
  location: location
  properties: {
    protectedParameters: [{
        name: VAR_1
        value: VALUE_1
    }]
    source: {
      script: '/oops'
    }
  }
}

if (configPart1.properties.instanceView.exitStatus) {
    throw error
}

Author:	matferrari-msft
Assignees:	-
Labels:	enhancement, Needs: Triage :mag:, Service Attention, Compute - VM
Milestone:	-

[nikhilpatel909]

ack, reviewing it

[matferrari-msft]

@nikhilpatel909 Is there an update on this? Thanks!