You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
First of all, I want to say thank you for your module! Very useful module and I use it!
I have a suggestion.
I see that in new versions of the module when creating a NIC for a virtual machine, they are sorted in alphabetical order.
I think this is not a very good idea.
For example:
I deploy a server with 3 NIC and I want "PortGroup" for "Management-Network" to always be associated with the first interface in the system, ens192.
According to alphabetical sorting, "PortGroup" for "Management-Network" can be either on ens192 or ens256, and so on.
This complicates further use.
For example, there is a software/service that tries to work with ens192 interfaces, considering it "Management-Network", and so on.
Best regards,
The text was updated successfully, but these errors were encountered:
Use network_delimiter added back in Nov 2023 https://github.com/Terraform-VMWare-Modules/terraform-vsphere-vm/pull/157, it's in the current version. Two features were added, this would be referencing the second. Basically, if you set the delimiter to some non-used character, it will use the whole string when sorting alphabetically, but use the text after the delimiter to assign the portgroup name to the first/second interface (and so on).
Now you have it sorted by the numbers, but the portgroup assignment will be Management-Network for the first interface and Backup-Network for the second.
Hello,
First of all, I want to say thank you for your module! Very useful module and I use it!
I have a suggestion.
I see that in new versions of the module when creating a NIC for a virtual machine, they are sorted in alphabetical order.
I think this is not a very good idea.
For example:
I deploy a server with 3 NIC and I want "PortGroup" for "Management-Network" to always be associated with the first interface in the system, ens192.
According to alphabetical sorting, "PortGroup" for "Management-Network" can be either on ens192 or ens256, and so on.
This complicates further use.
For example, there is a software/service that tries to work with ens192 interfaces, considering it "Management-Network", and so on.
Best regards,
The text was updated successfully, but these errors were encountered: