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
vSphere 7.0 U1 introduced hardware version 18 and 7.0 U2 version 19 (see https://kb.vmware.com/s/article/1003746). I'm not sure if just updating the max. value to 19 is the best option here, or rather just removing this validation. If U3 comes with v20 another provider update is required. It would probably be better to treat this a a more opaque value.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked as resolved and limited conversation to collaborators
May 20, 2021
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
vSphere 7.0 U1 introduced hardware version 18 and 7.0 U2 version 19 (see https://kb.vmware.com/s/article/1003746). I'm not sure if just updating the max. value to 19 is the best option here, or rather just removing this validation. If U3 comes with v20 another provider update is required. It would probably be better to treat this a a more opaque value.
terraform-provider-vsphere/vsphere/virtual_machine_config_structure.go
Line 310 in 21e5d47
The text was updated successfully, but these errors were encountered: