@jasonberanek it looks like the DVS stuff won't be much of an issue at all, actually. The dc.network method actually returns both standard port groups and distributed port groups, so we can just use that instead of dc.networkFolder.childEntity. I'll have a pull request to the branch in your fork soon.

The only situation in which having a DVS could screw you over is if you had both an SVS and DVS port group with the same name (which is valid, since the namespace of the distributed port groups is scoped to the DVS itself. In that case, the dc.network.find operation would only return the first match, which might be unexpected. Incidentally, I do have that situation, but I've decided that is a stupid move on my part to set it up that way, and is likely a very edge case. In any event the DVS port group names are really just friendly names, and so are easy to change and don't impact anything runtime-y.