Skip to content

Conversation

@brianvanderlugt
Copy link

Purpose

  • Fixes initializing VM data disks when there is only 1 OS disk as part of the VM image.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

When deploying a VMSS with the following vmSku and image reference, this script failed to initialize my disk as there is only the C: drive and no Temp D: drive.

    "type": "Microsoft.Compute/virtualMachineScaleSets",
      "apiVersion": "2020-12-01",
      "location": "westus",
      "dependsOn": [],
      "sku": {
        "name": "Standard_D4s_v4",
        "tier": "Standard",
        "capacity": "3"
      },
      "properties": {
        "virtualMachineProfile": {
          "priority": "Regular",
          "storageProfile": {
            "imageReference": {
              "publisher": "MicrosoftWindowsServer",
              "offer": "WindowsServer",
              "sku": "2019-Datacenter-with-Containers",
              "version": "latest"
           },
      }
}

Some VMs don't initialize with a temp D drive. This handles updating
and initializing VM drives and setting letters regardless
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant