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
I would like to add that the label documentation should more clearly explain the NIC you want to interface to connect to. At the same time, perhaps the deviceName could actually be utilized in the script so we can name our interfaces.
type networkInterface struct {
deviceName string
label string
ipv4Address string
ipv4PrefixLength int
ipv4Gateway string
ipv6Address string
ipv6PrefixLength int
ipv6Gateway string
adapterType string // TODO: Make "adapter_type" argument
macAddress string
}
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Abstract
This is either a documentation bug or a badly named field.
Terraform Version
I run
Terraform v0.7.0-dev (f312ba1f28b91deb988e41778f840703f418bcdc+CHANGES)
Affected Resource(s)
vsphere_virtual_machine
Terraform Configuration Files
Expected Behavior
The
label
should be the label of the nic OR the field shall be renamed asconnect_to
or something approaching.Actual Behavior
The
label
field designates which network you want to connect the NIC to. There is no way to specify a name for the NIC.Steps to Reproduce
terraform apply
Important Factoids
vSphere 5.5, Terraform in a dev branch (working on the vSphere provider)
References
None.
The text was updated successfully, but these errors were encountered: