Add new data source: vsphere_distributed_virtual_switch #170
Conversation
|
Any ETA on some MR for those? (days, weeks, monthes?) |
|
Hi @ze42, I have some PoC code for it and was planning to push it forward in the next couple of weeks unless someone from HC wants to take the lead and get it through a bit faster. |
|
@ze42, echoing @jorgenunez's approximate roadmap here, right now we are working on tagging support but wrapping up the DVS stuff is a priority. This will probably get more attention next week. |
vancluever
added
enhancement
|
We really would love the additional feature for vsphere_distributed_virtual_portgroup. Could we help and test your PoC code? |
Caught this was running a more complex test of the DVS data source. Quick fix that prevents a crash - and makes things correct of course.
* Refactor for updates since PR was submitted. * Make datacenter optional if path is properly supplied (path lookup workflow is the same as the DVS resource import, where datacenter is not necessary either). * Add uplinks as an exported variable. * Add tests. * Update documentation.
|
Hey @jorgenunez! Thanks for this as well - I have made some updates to it to reflect the final state of the DVS resource and am merging it now. Good work on this! |
ghost
locked and limited conversation to collaborators
New data source
vsphere_distributed_virtual_switch. Required for futurevsphere_distributed_virtual_portgroupin case that those aren't created with Terraform.Depends on some helper code from #135