Add privateIPAddressPrefixLength for az vmss command json output/input

[alyssa1303]

Related command

az vmss update [--add]

Is your feature request related to a problem? Please describe.

Can we add support to create prefix IP address when adding secondary ip configuration using az vmss update --add command? Currently, the json output of the command doesn't include a property called privateIPAddressPrefixLength, so even when I added it, it'll be ignored and the created secondary ipconfig will just create a single IP instead of a prefix IP address range.

When running this command, it's supposed to create ipconfig with prefix address range instead of a single IP address

az vmss update --name test --resource-group $RG \
        --add virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations '{"name": "ipconfig2", "primary": false, "privateIpAddressPrefixLength": "28", "privateIpAddressVersion": "IPv4", "subnet": {"id": "'"$subnet_id"'", "resourceGroup": "'"$RG"'"}}'

Describe the solution you'd like

            {
              "applicationGatewayBackendAddressPools": null,
              "applicationSecurityGroups": null,
              "loadBalancerBackendAddressPools": null,
              "loadBalancerInboundNatPools": null,
              "name": "<ipconfig-name>",
              "primary": false,
              "privateIpAddressVersion": "IPv4",
              "privateIpAddressPrefixLength": "28", <- this line
              "publicIpAddressConfiguration": null,
              "subnet": {
                "id": "<subnet-id>",
                "resourceGroup": "<resource-group>"
              }
            }

Describe alternatives you've considered

Additional context

[yonzhan]

Thank you for opening this issue, we will look into it.

[yanzhudd]

Hi @alyssa1303 could you please provide more information by filling out this template?
https://github.com/Azure/azure-cli/issues/new?assignees=&labels=feature-request&projects=&template=Service_team_request.yml
We'll need this information in order to move forward with developing the feature. Once it’s provided, we can create a plan accordingly. Thanks!