How to select VM T-shirt size in Azure ARM Template












0














I have a VM deloyment template where i am defining the VM size as T-Shirt Sizes for example small = Standard_DS2_v2, medium = Standard_E4s_v3 and large = Standard_E4s_v3.



I have defined them as an array as shown below in variables section



 "parameters": {
"vmSpecs": {
"type": "array"
}
},

"variables": {
"vmSizeType" :[{
"small" : "Standard_DS2_v2",
"medium": "Standard_E4s_v3",
"large" : "Standard_E32s_v3"
}]
},

"resources": [
{
"name": "[parameters('vmSpecs')[copyIndex()].vmName]",
"type": "Microsoft.Compute/virtualMachines",
"location": "[resourceGroup().location]",
"apiVersion": "2018-06-01",
"dependsOn": [
"VMNIC0Copy",
"[variables('storageAccountName')]"
],
"copy": {
"name": "VMCopy",
"count": "[length(parameters('vmSpecs'))]"
},

"properties": {
"licenseType": "[parameters('vmSpecs')[copyIndex()].licenseType]",
"hardwareProfile": {
"vmSize": "[parameters('vmSpecs')variables('vmSizeType')[copyIndex()].vmSize[1]]"
}
}


In parameters file



"vmSpecs": {
"value": [
{ //vm01
"vmName": "test",
"dnsDomain": "domain.com",
"vmSize": "medium"
}
}


My question is how do i input vmSize and it selects the size based on what that has been defined










share|improve this question



























    0














    I have a VM deloyment template where i am defining the VM size as T-Shirt Sizes for example small = Standard_DS2_v2, medium = Standard_E4s_v3 and large = Standard_E4s_v3.



    I have defined them as an array as shown below in variables section



     "parameters": {
    "vmSpecs": {
    "type": "array"
    }
    },

    "variables": {
    "vmSizeType" :[{
    "small" : "Standard_DS2_v2",
    "medium": "Standard_E4s_v3",
    "large" : "Standard_E32s_v3"
    }]
    },

    "resources": [
    {
    "name": "[parameters('vmSpecs')[copyIndex()].vmName]",
    "type": "Microsoft.Compute/virtualMachines",
    "location": "[resourceGroup().location]",
    "apiVersion": "2018-06-01",
    "dependsOn": [
    "VMNIC0Copy",
    "[variables('storageAccountName')]"
    ],
    "copy": {
    "name": "VMCopy",
    "count": "[length(parameters('vmSpecs'))]"
    },

    "properties": {
    "licenseType": "[parameters('vmSpecs')[copyIndex()].licenseType]",
    "hardwareProfile": {
    "vmSize": "[parameters('vmSpecs')variables('vmSizeType')[copyIndex()].vmSize[1]]"
    }
    }


    In parameters file



    "vmSpecs": {
    "value": [
    { //vm01
    "vmName": "test",
    "dnsDomain": "domain.com",
    "vmSize": "medium"
    }
    }


    My question is how do i input vmSize and it selects the size based on what that has been defined










    share|improve this question

























      0












      0








      0







      I have a VM deloyment template where i am defining the VM size as T-Shirt Sizes for example small = Standard_DS2_v2, medium = Standard_E4s_v3 and large = Standard_E4s_v3.



      I have defined them as an array as shown below in variables section



       "parameters": {
      "vmSpecs": {
      "type": "array"
      }
      },

      "variables": {
      "vmSizeType" :[{
      "small" : "Standard_DS2_v2",
      "medium": "Standard_E4s_v3",
      "large" : "Standard_E32s_v3"
      }]
      },

      "resources": [
      {
      "name": "[parameters('vmSpecs')[copyIndex()].vmName]",
      "type": "Microsoft.Compute/virtualMachines",
      "location": "[resourceGroup().location]",
      "apiVersion": "2018-06-01",
      "dependsOn": [
      "VMNIC0Copy",
      "[variables('storageAccountName')]"
      ],
      "copy": {
      "name": "VMCopy",
      "count": "[length(parameters('vmSpecs'))]"
      },

      "properties": {
      "licenseType": "[parameters('vmSpecs')[copyIndex()].licenseType]",
      "hardwareProfile": {
      "vmSize": "[parameters('vmSpecs')variables('vmSizeType')[copyIndex()].vmSize[1]]"
      }
      }


      In parameters file



      "vmSpecs": {
      "value": [
      { //vm01
      "vmName": "test",
      "dnsDomain": "domain.com",
      "vmSize": "medium"
      }
      }


      My question is how do i input vmSize and it selects the size based on what that has been defined










      share|improve this question













      I have a VM deloyment template where i am defining the VM size as T-Shirt Sizes for example small = Standard_DS2_v2, medium = Standard_E4s_v3 and large = Standard_E4s_v3.



      I have defined them as an array as shown below in variables section



       "parameters": {
      "vmSpecs": {
      "type": "array"
      }
      },

      "variables": {
      "vmSizeType" :[{
      "small" : "Standard_DS2_v2",
      "medium": "Standard_E4s_v3",
      "large" : "Standard_E32s_v3"
      }]
      },

      "resources": [
      {
      "name": "[parameters('vmSpecs')[copyIndex()].vmName]",
      "type": "Microsoft.Compute/virtualMachines",
      "location": "[resourceGroup().location]",
      "apiVersion": "2018-06-01",
      "dependsOn": [
      "VMNIC0Copy",
      "[variables('storageAccountName')]"
      ],
      "copy": {
      "name": "VMCopy",
      "count": "[length(parameters('vmSpecs'))]"
      },

      "properties": {
      "licenseType": "[parameters('vmSpecs')[copyIndex()].licenseType]",
      "hardwareProfile": {
      "vmSize": "[parameters('vmSpecs')variables('vmSizeType')[copyIndex()].vmSize[1]]"
      }
      }


      In parameters file



      "vmSpecs": {
      "value": [
      { //vm01
      "vmName": "test",
      "dnsDomain": "domain.com",
      "vmSize": "medium"
      }
      }


      My question is how do i input vmSize and it selects the size based on what that has been defined







      json azure azure-devops arm-template






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 19:43









      raptor85raptor85

      552310




      552310
























          1 Answer
          1






          active

          oldest

          votes


















          1














          like you normally would (using dot notation) access object properties in almost any language:



          "vmSizeType" :{ << should be an object, you only make it harder making it an array
          "small" : "Standard_DS2_v2",
          "medium": "Standard_E4s_v3",
          "large" : "Standard_E32s_v3"
          }
          ...
          "vmSize": "[variables('vmSizeType')[parameters('vmSpecs')[copyIndex()].vmSize]]"
          ^^ tshirt variable ^ ^^ input parameter ^^ iteration ^^ property
          ^ get property defined dynamically, have to use syntax instead of dot notation
          for statichardcoded property name you can use dot notation:
          variables('vmSizeType').small


          if you need tshirt variable to be array (no reason), you'd have to account for that as well






          share|improve this answer





















          • cool it worked, thanks for the info
            – raptor85
            Nov 19 '18 at 21:43











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381578%2fhow-to-select-vm-t-shirt-size-in-azure-arm-template%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          like you normally would (using dot notation) access object properties in almost any language:



          "vmSizeType" :{ << should be an object, you only make it harder making it an array
          "small" : "Standard_DS2_v2",
          "medium": "Standard_E4s_v3",
          "large" : "Standard_E32s_v3"
          }
          ...
          "vmSize": "[variables('vmSizeType')[parameters('vmSpecs')[copyIndex()].vmSize]]"
          ^^ tshirt variable ^ ^^ input parameter ^^ iteration ^^ property
          ^ get property defined dynamically, have to use syntax instead of dot notation
          for statichardcoded property name you can use dot notation:
          variables('vmSizeType').small


          if you need tshirt variable to be array (no reason), you'd have to account for that as well






          share|improve this answer





















          • cool it worked, thanks for the info
            – raptor85
            Nov 19 '18 at 21:43
















          1














          like you normally would (using dot notation) access object properties in almost any language:



          "vmSizeType" :{ << should be an object, you only make it harder making it an array
          "small" : "Standard_DS2_v2",
          "medium": "Standard_E4s_v3",
          "large" : "Standard_E32s_v3"
          }
          ...
          "vmSize": "[variables('vmSizeType')[parameters('vmSpecs')[copyIndex()].vmSize]]"
          ^^ tshirt variable ^ ^^ input parameter ^^ iteration ^^ property
          ^ get property defined dynamically, have to use syntax instead of dot notation
          for statichardcoded property name you can use dot notation:
          variables('vmSizeType').small


          if you need tshirt variable to be array (no reason), you'd have to account for that as well






          share|improve this answer





















          • cool it worked, thanks for the info
            – raptor85
            Nov 19 '18 at 21:43














          1












          1








          1






          like you normally would (using dot notation) access object properties in almost any language:



          "vmSizeType" :{ << should be an object, you only make it harder making it an array
          "small" : "Standard_DS2_v2",
          "medium": "Standard_E4s_v3",
          "large" : "Standard_E32s_v3"
          }
          ...
          "vmSize": "[variables('vmSizeType')[parameters('vmSpecs')[copyIndex()].vmSize]]"
          ^^ tshirt variable ^ ^^ input parameter ^^ iteration ^^ property
          ^ get property defined dynamically, have to use syntax instead of dot notation
          for statichardcoded property name you can use dot notation:
          variables('vmSizeType').small


          if you need tshirt variable to be array (no reason), you'd have to account for that as well






          share|improve this answer












          like you normally would (using dot notation) access object properties in almost any language:



          "vmSizeType" :{ << should be an object, you only make it harder making it an array
          "small" : "Standard_DS2_v2",
          "medium": "Standard_E4s_v3",
          "large" : "Standard_E32s_v3"
          }
          ...
          "vmSize": "[variables('vmSizeType')[parameters('vmSpecs')[copyIndex()].vmSize]]"
          ^^ tshirt variable ^ ^^ input parameter ^^ iteration ^^ property
          ^ get property defined dynamically, have to use syntax instead of dot notation
          for statichardcoded property name you can use dot notation:
          variables('vmSizeType').small


          if you need tshirt variable to be array (no reason), you'd have to account for that as well







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 19 '18 at 19:56









          4c74356b414c74356b41

          25k42050




          25k42050












          • cool it worked, thanks for the info
            – raptor85
            Nov 19 '18 at 21:43


















          • cool it worked, thanks for the info
            – raptor85
            Nov 19 '18 at 21:43
















          cool it worked, thanks for the info
          – raptor85
          Nov 19 '18 at 21:43




          cool it worked, thanks for the info
          – raptor85
          Nov 19 '18 at 21:43


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381578%2fhow-to-select-vm-t-shirt-size-in-azure-arm-template%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          SQL update select statement

          'app-layout' is not a known element: how to share Component with different Modules