Terraform vSocket 2-NIC Module issues

Hi Michael,

We have a few different areas and topics so I will try to break them down and answer the best I can, also the module has been through some major upgrades fixing some of your requests.
 
There are specific limitations in the naming of the Azure resources and we build a custom name taking into account these limitations automatically using the site_name variable as a base.
 
The new resource type azurerm_linux_virtual_machine is now in use and updated for this module.
As you have stated there is the option to specify vnet and resource groups which are already created.
 
Currently the use of custom naming in the module for vSocket is not possible and main reason for this is to allow the same functionality as our other deployment methods like the Marketplace. That being said if you only require custom naming for the vSocket resources, I am sure this can be added as part of a future update.
 
In reference to the availability zones it seems the newest update emitted the use of these I will enquire why this may have happened and look to add them back again.
 
The custom or changes in the discs is a different requirement as currently what we deploy is the only supported and tested type.
I am more than happy to raise an RFE on your behalf so that different disk types can be used for specific requirements, but this is likely to be something that will take some time before it is available. It requires time and development from all areas of Cato, unlike the other discussed areas can be updated in the Terraform module as it is already a supported feature or use case.
 
There is also discussions on the single 2nic vSocket but I also do not have any timeline for this currently.
 
Please let me know if I have missed anything or you have any further follow ups.

Thanks Rob